Verified against Semitexa Ultimate 2026.09.19.1020

Locale Setup

Semitexa keeps locale as an explicit contract. Even when phase 1 ships English-only documentation, the runtime should still make locale handling visible and deterministic.

Canonical flow

1. Define the default locale.
2. Declare supported locales.
3. Wire translation catalogs.
4. Verify one translation in Twig so the path is proven.

What to preserve

• locale resolution remains explicit
• fallback behavior is deterministic
• translation keys do not turn into scattered string guesses

Why this matters

Multilingual support is easiest to preserve when the first locale setup is explicit, even if only English content is active at the beginning.