Path
ez.no / ezpublish / documentation / development / extensions / translation
Translation
These documentation pages are no longer maintained. Please visit the new documentation site.
Note: Using x18n is only required for eZ publish 3.1 or lower. In 3.2 the extension should use the i18n operator instead.
Having translations for extension design or code is quite similar to translations for the kernel. The main difference is the use of the x18n operator as opposed to the i18n operator and the placement of the translation file.
The first thing you must do is to make sure i18n is used in your design. The first parameter defines the name of your extension and the rest is similar to the i18n operator. For instance let's assume our extension is called myextension we then create a translation line in one of our templates.
{"Translations in extensions"|i18n("myextension")}
The next time the site is run the translation file will be looked for in extension/myextension/translations and will be used if found.
To create the untranslated translation files for a extension please run the following line in your shell.
ezroot> ezlupdate.exe -u --extension extension/myextension
Creating the untranslated and the our language file
ezroot> ezlupdate.exe -u --extension extension/myextension ger-DE
Comments
INI setting
Eirik Johansen
Wednesday 08 December 2004 12:25:40 pm
[RegionalSettings]
TranslationExtensions[]=myextension