Add i18n completeness checker after language architecture is defined #10

New issue

Open

opened 2026-08-11 20:40:01 +02:00 by michael · 0 comments

michael commented

2026-08-11 20:40:01 +02:00

Owner

Goal

Provide an i18n completeness/checking tool for berhtjan language resources once the language-resource architecture has been defined.

This issue is intentionally blocked by #6. The checker must be derived from the language model agreed there rather than inventing a parallel file format or lookup mechanism.

Session rationale

During the berhtjan 2.1 migration, language resolution was made explicit (lang / default_lang, no silent fallback), but the source, ownership, registration and runtime delivery of multilingual resources are still unresolved.

A checker for missing translations is useful, but its actual input format and validation rules depend on that architecture. The implementation therefore belongs after the decisions in #6.

Scope

Track the i18n-checking tool as follow-up work to #6.
Once #6 defines the language-resource model, determine which resources/keys the checker must inspect.
Detect missing translations relative to a selected/default language.
Report incomplete language resources without inventing silent fallback behavior.
Decide during implementation whether the checker remains in daw-modul-berhtjan-cli or should move to a dedicated/shared tool repository; do not pre-empt that decision here.
Keep the checker compatible with the language/resource contract established by #6.

Out of scope for now

Defining a new translation file format.
Defining the language-resource runtime architecture independently of #6.
Hardcoding de, en, or any other language as a universal default.

Acceptance criteria

Issue #6 has defined the language-resource model required by the checker.
Checker validates language-resource completeness against that model.
A selected/default language can be used as the completeness reference.
Missing translations are reported explicitly.
No language is hardcoded as the universal fallback.
Repository placement is confirmed from the resulting architecture before implementation is finalized.
Tests cover complete and incomplete multilingual resource sets.

Coordination

Blocked by: #6 — language resolution/resource architecture.

This issue deliberately follows #6 instead of defining competing i18n semantics.

## Goal Provide an i18n completeness/checking tool for berhtjan language resources once the language-resource architecture has been defined. This issue is intentionally blocked by #6. The checker must be derived from the language model agreed there rather than inventing a parallel file format or lookup mechanism. ## Session rationale During the berhtjan 2.1 migration, language resolution was made explicit (`lang` / `default_lang`, no silent fallback), but the source, ownership, registration and runtime delivery of multilingual resources are still unresolved. A checker for missing translations is useful, but its actual input format and validation rules depend on that architecture. The implementation therefore belongs after the decisions in #6. ## Scope - Track the i18n-checking tool as follow-up work to #6. - Once #6 defines the language-resource model, determine which resources/keys the checker must inspect. - Detect missing translations relative to a selected/default language. - Report incomplete language resources without inventing silent fallback behavior. - Decide during implementation whether the checker remains in daw-modul-berhtjan-cli or should move to a dedicated/shared tool repository; do not pre-empt that decision here. - Keep the checker compatible with the language/resource contract established by #6. ## Out of scope for now - Defining a new translation file format. - Defining the language-resource runtime architecture independently of #6. - Hardcoding `de`, `en`, or any other language as a universal default. ## Acceptance criteria - [ ] Issue #6 has defined the language-resource model required by the checker. - [ ] Checker validates language-resource completeness against that model. - [ ] A selected/default language can be used as the completeness reference. - [ ] Missing translations are reported explicitly. - [ ] No language is hardcoded as the universal fallback. - [ ] Repository placement is confirmed from the resulting architecture before implementation is finalized. - [ ] Tests cover complete and incomplete multilingual resource sets. ## Coordination Blocked by: #6 — language resolution/resource architecture. This issue deliberately follows #6 instead of defining competing i18n semantics.

michael added the

coordination/cross-repo

labels