Translation in Zikula
Zikula uses the native Symfony translation system. Please refer to Symfony docs for more information about Symfony features.
Paths and file names used by Symfony translator
Zikula core system
Bundles (modules, themes etc.)
Symfony translator loaders
Symfony comes with standard file format loaders:
- ArrayLoader - to load catalogs from PHP arrays.
- CsvFileLoader - to load catalogs from CSV files.
- IcuDatFileLoader - to load catalogs from resource bundles.
- IcuResFileLoader - to load catalogs from resource bundles.
- IniFileLoader - to load catalogs from INI files.
- JsonFileLoader - to load catalogs from JSON files.
- MoFileLoader - to load catalogs from gettext files.
- PhpFileLoader - to load catalogs from PHP files.
- PoFileLoader - to load catalogs from gettext files.
- QtFileLoader - to load catalogs from QT XML files.
- XliffFileLoader - to load catalogs from Xliff files.
- YamlFileLoader - to load catalogs from Yaml files.
From Symfony translator documentation:
Each time you create a new translation resource (or install a bundle that includes a translation resource), be sure to clear your cache so that Symfony can discover the new translation resources.
Translations are cached in
Let's look at a website with 3 languages:
en (strings are in
All languages are enabled but some translations are missing for some strings.
Normally it would show English as default because strings are in English.
The fallback locale is a feature that reads translator 'fallback' setting from config.yaml
and sets this as locale to show instead the one that is missing.
So when viewing a German site in Polish language and Polish translations are not complete
while the German is, it will show German translations instead. This will happen only
when translator fallback setting locale is set to
de. At the end there is always an English string.