Erro interno do servidor
``` ## Localized validation messages Every validator default message routes through the `validation` domain. The English defaults are the keys — a complete pt-BR catalog: ```php '{field} é inválido.', '{field} is required.' => '{field} é obrigatório.', '{field} must be a boolean.' => '{field} deve ser um booleano.', '{field} must be a valid date.' => '{field} deve ser uma data válida.', '{field} must be a valid date in the format {format}.' => '{field} deve ser uma data válida no formato {format}.', '{field} must be a valid email address.' => '{field} deve ser um endereço de e-mail válido.', '{field} must be a valid URL.' => '{field} deve ser uma URL válida.', '{field} must be an integer.' => '{field} deve ser um número inteiro.', '{field} must be at least {limit}.' => '{field} deve ser no mínimo {limit}.', '{field} must be at most {limit}.' => '{field} deve ser no máximo {limit}.', '{field} must be at most {limit} bytes.' => '{field} deve ter no máximo {limit} bytes.', '{field} must be one of the allowed values.' => '{field} deve ser um dos valores permitidos.', '{field} must have an allowed extension.' => '{field} deve ter uma extensão permitida.', '{field} must have an allowed MIME type.' => '{field} deve ter um tipo MIME permitido.', '{field} confirmation does not match.' => 'A confirmação de {field} não confere.', '{field} has an invalid format.' => '{field} tem um formato inválido.', ]; ``` ```php use Bootgly\ADI\Validation; use Bootgly\ADI\Validators\Required; Language::$locale = 'pt-BR'; $Validation = new Validation( source: [], rules: ['email' => [new Required]] ); $Validation->errors['email'][0]; // email é obrigatório. ``` Custom `message:` overrides also pass through the catalogs (so they are translatable keys too) and gain `{field}` placeholder support; without a catalog entry they render verbatim, exactly as before. ## Templates The `@translate` directive is the canonical template form — output is **escaped by default** (translations interpolate user data). Arguments pass verbatim to `Language::translate()`, so named arguments work: ```text @translate 'Welcome, {name}!', ['name' => $name]; @translate '{count} result|{count} results', count: $total; @translate 'Sign in', domain: 'auth'; ``` Escape the directive itself with `@@translate`. For trusted raw HTML translations, fall back to the raw output directive: `@> \Bootgly\ABI\Data\Language::translate('key');`. ## Localized error pages In Production/Staging the built-in clean error page and the JSON error body translate the HTTP reason phrase through the `errors` domain — the reason phrase is the key: ```php 'Não encontrado', 'Internal Server Error' => 'Erro interno do servidor', ]; ``` The HTML `lang` attribute follows the active locale. The **wire status line stays English** (`HTTP/1.1 500 Internal Server Error`) — only body text is localized, per RFC semantics. Fully custom pages keep working: a `views/errors/{code}.template.php` view is rendered with the request locale already active, so `@translate` inside it just works. ## Console and scripts Outside the Web platform, assign the locale explicitly. `Locales::normalize()` is POSIX-aware, so the environment locale is one line away: ```php use function getenv; use Bootgly\ABI\Data\Language; Language::load(__DIR__ . '/catalogs'); Language::$locale = Language::negotiate([(string) getenv('LANG')]); // pt_BR.UTF-8 → pt-BR ``` ## Caveats - **Catalogs cache per worker.** Files are `require`d once per (root, locale, domain) and held for the worker lifetime (opcache-friendly). Editing a catalog on a long-running server requires a reload/restart. - **Deferred responses (Fibers).** The active locale is per-request worker state; a deferred continuation may resume after a later request re-negotiated it. Capture translated strings before deferring. - **Source language edits orphan translations.** Keys are the source text (gettext trade-off): rewording the English message renames the key — update catalogs together with the source. ## Reference ### `Bootgly\ABI\Data\Language` ```php public static string $source = 'en'; ``` The language the source strings (keys) are written in. Lookups targeting it short-circuit the catalogs. ```php public static string $locale = 'en'; ``` The active locale. Assign directly; on the HTTP server it is re-negotiated (and therefore reset) on every request once catalogs are registered. ```php public static array $roots = []; ``` Registered catalog roots, in registration order. Read it as the "i18n enabled" probe; manage it via `load()`. ```php public static function load (string $root): void ``` Registers a catalogs root directory (`{root}/{locale}/{domain}.php`). Roots registered later take priority over earlier ones. Duplicates are ignored. ```php public static function translate (string $message, array $substitutions = [], null|int|float $count = null, string $domain = 'app', null|string $locale = null): string ``` Translates a source message to the active (or given) locale. Never throws: on any miss the message itself is the result. `$count` selects a `|`-separated plural form and auto-fills `{count}`; `$domain` picks the catalog file (`app` by default); `$locale` overrides the active locale for this call only. No output escaping is performed. ```php public static function negotiate (array $preferred): string ``` Chooses the best available locale (the registered roots' locale directories) for the ordered preferences — e.g. `$Request->languages`. Pure: returns the choice (falling back to `Language::$source`) and never mutates state. ```php public static function reset (): void ``` Restores the boot state: drops registered roots and caches; `$source`/`$locale` back to `en`. Test-lifecycle helper. ### `Bootgly\ABI\Data\Language\Locales` ```php public static function normalize (string $locale): string ``` Normalizes a BCP 47 or POSIX locale tag to canonical form (`pt_BR.UTF-8` → `pt-BR`, `PT-br` → `pt-BR`). `C`, `POSIX`, empty or malformed input normalizes to `''`. ```php public static function chain (string $locale): array ``` Expands a normalized tag into its lookup chain by progressive truncation: `pt-BR` → `['pt-BR', 'pt']`. ```php public static function choose (array $preferred, array $available): null|string ``` RFC 4647 lookup (lite): per preference — exact match, truncation (`pt-BR` matches `pt`), regional expansion (`pt` matches the first `pt-*`), `*` wildcard. Client order wins. Returns the matching available entry as given, or `null`. ### `@translate` directive ```text @translate