Implemented #18185: add in share/locale/*.ini all translations of all languages supported by eZ #145
Conversation
…All Visible" button
…unctions" - added code before the daemon starts to check if the functions are available - added documentation on how to override the disabled functions
…ource Changed $matchFilesArray to the correct $matchFileArray
… extension.xml, to have same behavior as ezinfo.php
Fixed 18427: doc issue, file.ini instead of php.ini
Implemented #18381: add description/author in ezinfo/about when using extension.xml, to have same behavior as ezinfo.php
…site.ini as example is wrong
If there are no classes to generate autoloads for in extension/, a warning was thrown about the progressbar.
…ile checking DB consistency
… languages supported by eZ
|
Hi! [Translation_ara-SA] [Translation_cat-ES] |
|
@trolek yes you're completely right, it would be much more generic, I'll change the pull request to respect this form However first, @bdunogier @glye @andrerom and others, what do you think about this form ? would you think at an even more generic form than this one, exposed by @trolek ? |
|
I like the idea, but how do you intend to read these settings? I'm not sure if ezini() can be used to read locales from a template. Perhaps you will need to modify l10n() or add a new operator for extracting this? There's also the question of whether the original [RegionalSettings] should be marked for deprecation, if we merge this. |
Several remarks:
1/ it's a proposal... However as it's already possible to have all countries in all languages thanks to country.ini, it would be nice I guess to have the same thing for the languages!
2/ the languages don't contain any reference to the country, that way, the developer may add the country or not near the language if (s)he really wants it (quite boring in fact on a bilingual website for example, to have French / English (Great Britain)... in general, the webmaster just wants to say French / English in that example)
3/ the translations have not been generated with automatic translation (which may not be accurate), they have been get by fetching the list of languages supported by Google Translate (that includes all languages supported by eZPublish), with a navigator that sequentially accepts english, then chinese, then french, etc... (use of Accept-Language header). As a result the list of translations should be accurate