Michal Čihař a écrit :
Hello all
while looking at possibilities for web based translation tool, I (again) started to think about switching to gettext based system from current string based. The good thing is that the migration should not be hard (I already migrated one small PHP project to gettext).
Pros:
- standard format, what means that translators can use translation editors or other tools
- support for fuzzy translations - when we have to change English text, translators will know this and translation can be also fixed
- support for plural forms
- texts are directly in place where they are used
- not used strings will be automatically dropped
Cons:
- gettext extension in PHP is bad, we would have to use implementation in PHP (we can use http://savannah.nongnu.org/projects/php-gettext/)
- more complicated releases/SVN deployment - you have to compile po files to binary form
What do you think?
In case we decide to switch I volunteer to do the migration.
Hi Michal, Would this have an impact on performance, for example? And what about you wrote previously: ---------- [*] I'd really prefer to migrate to gettext based solution for phpMyAdmin, but this seems unlikely, mostly because gettext as integrated in PHP is quite painful. Once you load translation, it is kept opened and any changes in the file lead to segfault and any replacing of the file is deleted. So the only way to make it see updated translation is to restart PHP (or Apache if you use mod_php). ----------
Marc