I18n and l10n

The application has two ways to deal with multi-lingual texts:

Interface strings are handled via Zend_translate
Questionnaire content is handled via a modified version of the Doctrine I18n behavior

The default language is English. Active languages are defined in: application/classes/Webenq/Language.php (currently: en, nl, & languages from database).

Zend_translate

Strings are translated by using Zend_translate
http://framework.zend.com/manual/1.12/en/zend.translate.html
We use the gettext variant.
In application/translation/webenq4.pot we have a set of translatable strings. These strings are mostly harvest by scanning the code (.php and .phtml)for:
setMessage, _ translate, setLabel, setLegend, _refresh, setValue, append, t
t is a method we wrote to perform the translation, customized for our needs.
Some strings are not found in the code (eg controller/methods used in user management). To be able to find those strings when we harvest the strings, we add these strings in a3pplications/translation/WebenqManualStrings.php.

We use poedit to scan the code for translatable strings. These are stored in application/translations/webenq4.pot.
To translate, we use this file to scan for new strings.

zend_validate

We use zend-validate to validate forms we want to use the translations shipped with the zend-framework (https://github.com/zendframework/zf2/tree/master/resources/languages (assuming we use zf2)), but this is array based, so we combine multiple sources

javascript

http://docs.jquery.com/UI/Datepicker/Localization (http://jqueryui.com/datepicker/#localization)
translations for datapicker can be found in the development bundle : /jquery-ui-x.y.z.custom/development-bundle/ui/i18n/
@todo always the dutch translation is used see also https://www.pivotaltracker.com/story/show/41151863

WebEnq

I18n and l10n

Zend_translate

zend_validate

javascript

See also