lang.php library

Path in the Gestor bibliotecas/lang.php

lang.php translates the messages of internal scripts: the database updater, the resource compiler, the plugin installer. It plays no part in translating the site or the admin panel, which use text variables (gestor_variaveis()) and the resources/<language>/ folder.

It is not in the library registry: the scripts include it with require_once.

How it works

• When included, it sets $GLOBALS['lang'] (default pt-br) and loads $GLOBALS['dicionario'] with carregar_dicionario().

• carregar_dicionario($lang = 'pt-br', $base = '') reads gestor/bibliotecas<base>/<lang>.json. That file does not exist in the bibliotecas/ folder, so the default dictionary is always empty.

• set_lang($lang) changes the language and reloads the dictionary (empty, for the same reason).

• __t($key, $replacements = []) returns the translation or, without one, the key itself. Each replacement substitutes {name} and :name.

The real dictionaries live next to each script, which merges them after set_lang():

set_lang('pt-br');
$file = __DIR__ . '/lang/' . $GLOBALS['lang'] . '.json';
if (is_file($file)) {
    $GLOBALS['dicionario'] = array_merge($GLOBALS['dicionario'], json_decode(file_get_contents($file), true));
}
echo __t('_compare_summary', ['tabela' => 'paginas', 'ins' => 3]);

Existing folders: controladores/atualizacoes/lang/, controladores/plugins/lang/ and controladores/agents/arquitetura/lang/.

Pitfalls

• The resource compiler (atualizacao-dados-recursos.php) calls set_lang('pt-br') but does not merge its lang/ folder: its messages come out as the raw key (_map_file_not_found).

• The :name replacement also hits prefixes: with ['id' => 5], :identifier becomes 5entifier. Prefer {name}.

• The functions are declared inside if (!function_exists(…)): if other code already defined __t(), this library's version is ignored.

Functions

carregar_dicionario($lang = 'pt-br', $base = '')

__t($key, $replacements = [])

set_lang($lang)