i18n is the result of the great work of several people:
- mauser implementing i18n in Piwik.
- Noah managing all the translators & reviewers
- all the translators (more than 50 contributors!!)
We still have some work to make it perfect
- review the english strings
We haven't really done a proper review of the existing english translation on which every new translation is based. Some texts are not clear, too verbose, or not verbose enough.
- column label translations
The column label translations are on a per plugin basis. example: the Label column can either be "Action" or "Country". Currently some general column renaming are done in modules/ViewDataTable/Html.php but we should do this for every datatable that requires a custom label name (most of them do)
- date translations
Currently we rely on system dates, but it seems some php installation don't have the right locale installed, therefore visitors see the date in the wrong language. Do we really set the right language for php to pick up the date?
- graph translations (see related ticket #84)
it seems the graph API is not stable yet, maybe we can wait to have a more stable API / features set to think about it
- support for right to left languages
- add conditional css style that will overload text classes/ids
- direction: rtl
- text-align: right (when original is left)
- add definition in translation file indicating what kind of langauge we load (rtl,ltr)
- Example of a custom RTL CSS
Please, if you have any other point you want to be fixed concerning i18n, post a comment