Follow-up: adopt daw_i18n/v1 for berhtjan-cli's own UI strings #11

New issue

Open

opened 2026-08-12 20:32:58 +02:00 by michael · 0 comments

michael commented

2026-08-12 20:32:58 +02:00

Owner

Goal

Track follow-up work in berhtjan-cli resulting from the daw_i18n/v1
contract (new) and the daw_error/v1 and daw_event/v1 updates in
DAW/daw-contracts.

Background

This is a direct continuation of #6 (language resolution) and #5
(hardcoded UI strings in render.lua/dispatch/display.lua). daw_i18n/v1
is now a real, checked-in contract that can address the remaining part
of #6: how translatable UI text (not error/event text, not
contribution labels) is represented, stored, and resolved.

Questions to resolve here

Can render.lua's/dispatch/display.lua's/prompt.lua's hardcoded
strings ("(keine Eintraege)", "Available commands:", the confirm()
"[j/n]" suffix) be expressed as daw_i18n/v1 resources owned by
berhtjan-cli itself?
Discovery/loading of daw_i18n/v1 resource files is explicitly out of
scope of the contract itself -- berhtjan-cli would need its own
loading mechanism (or wait for a future module-manager-level
discovery mechanism, not yet designed).
daw_event/v1 gained optional message/resource_id -- does berhtjan-cli
produce or consume any events that should carry these?

Acceptance criteria

Decision: berhtjan-cli's own UI strings become daw_i18n/v1
resources, or this is deferred pending discovery mechanism
If proceeding: resource files created, render.lua/dispatch/
display.lua/prompt.lua updated
#5 and #6 status reassessed against this decision

References

DAW/daw-contracts daw_i18n/v1
DAW/daw-contracts daw_error/v1
DAW/daw-contracts daw_event/v1
DAW/daw-modul-berhtjan-cli#5
DAW/daw-modul-berhtjan-cli#6

## Goal Track follow-up work in berhtjan-cli resulting from the daw_i18n/v1 contract (new) and the daw_error/v1 and daw_event/v1 updates in DAW/daw-contracts. ## Background This is a direct continuation of #6 (language resolution) and #5 (hardcoded UI strings in render.lua/dispatch/display.lua). daw_i18n/v1 is now a real, checked-in contract that can address the remaining part of #6: how translatable UI text (not error/event text, not contribution labels) is represented, stored, and resolved. ## Questions to resolve here - Can render.lua's/dispatch/display.lua's/prompt.lua's hardcoded strings ("(keine Eintraege)", "Available commands:", the confirm() "[j/n]" suffix) be expressed as daw_i18n/v1 resources owned by berhtjan-cli itself? - Discovery/loading of daw_i18n/v1 resource files is explicitly out of scope of the contract itself -- berhtjan-cli would need its own loading mechanism (or wait for a future module-manager-level discovery mechanism, not yet designed). - daw_event/v1 gained optional message/resource_id -- does berhtjan-cli produce or consume any events that should carry these? ## Acceptance criteria - [ ] Decision: berhtjan-cli's own UI strings become daw_i18n/v1 resources, or this is deferred pending discovery mechanism - [ ] If proceeding: resource files created, render.lua/dispatch/ display.lua/prompt.lua updated - [ ] #5 and #6 status reassessed against this decision ## References - DAW/daw-contracts daw_i18n/v1 - DAW/daw-contracts daw_error/v1 - DAW/daw-contracts daw_event/v1 - DAW/daw-modul-berhtjan-cli#5 - DAW/daw-modul-berhtjan-cli#6

michael added the

coordination/cross-repo

labels