[Feature] Add internationalisation

[papoteur-mga]

It would be interesting to have the application translated in more languages.
The php part can be translated using Zend_translate based on gettext system.
Strings can be quoted:
$translate->_("string to translate");
xgettext generates catalog .pot files.
msgmerge updates .po files.
msgformat generates compiled .mo catalog files which are used by Zend_translate.

[jjdejong]

That type of translation would apply to the UI. How would you translate the event and task names, which are contained in tables? The country table has three columns, for English, French and German. However it would not be conceivable to provide a column for each possible language.

One possibility could be to provide a separate sql script for each language, for updating the contents of the "name", "detail" and "notes" columns in the event_name table.

[alexthurgood]

Le 14/12/2016 à 10:25, Jean J. de Jong a écrit :

That type of translation would apply to the UI. How would you translate the event and task names, which are contained in tables? The country table has three columns, for English, French and German. However it would not be conceivable to provide a column for each possible language.

In the eOLF software, as far as I can tell, the Firebird database comes with dictionary tables for translated UI terms, however, this makes updates a painful and time consuming process, as anyone who has ever had to wait for an update to be processed can attest. Alex

[papoteur-mga]

How would you translate the event and task names, which are contained in tables? The country table has three columns, for English, French and German. However it would not be conceivable to provide a column for each possible language.

For such a field, we can perhaps provide a specific function which pick translation from database when lang is 'de' or 'fr', and from gettext/Zend_translate or a specific table for other languages.
If we use gettext, we should add a file which will be parsed by gettext to populate the .pot file. This file could be generated by a script which read the country, rules and event_name tables.

[papoteur-mga]

Hello,
A first stage of the internationalization landed on github. This concerns only the UI and php/HTML/javascript part.
I have to improve the login screen such that user can choose his language with a dropdown list. I got also warning when 'en' language is selected.

[jjdejong]

Great job! However, I pulled the update, but it broke my local repository. It apparently conflicted with changes I didn't push yet!

[jjdejong]

I pulled the latest version. I find the reactivity of the interface noticeably slower (the server seems to be doing a lot of work behind the scenes). The matter list takes several seconds to display the first time it's loaded. I also get this warning:
Notice: No translation for the language 'fr' available. in .../ZendFramework1/library/Zend/Translate/Adapter.php on line 458

[jjdejong]

I split the i18n branch from the master, because we are using the current master branch in production, and the i18n introduced too many glitches for a production use.