On Sun, Oct 19, 2008 at 1:44 AM, Dennis P. Nikolaenko <[EMAIL PROTECTED]> wrote: > Hello, > It has been suggested to use .po files for translation. This may be a > viable path, but it may introduce unneeded complexity.
I agree. I am also not sure if we want to add gettext in the mix. It's yet another dependency. > My real concern is about semantic changes in translatable strings. For > example, if en_US 'foo' has "Do bar" as a string and then later changed > to "Do baz", all other translations are left unchanged, because the > online translator does not detect the change in meaning. > To combat this, an original en_US string may be added as a comment after > the translated string. +1 (...) > After 'Change color' is changed to 'Change text color', translator > should offer to revise the translation in all locale files because the > comment in the locale file does not match the current en_US string. Maybe the translator needs some sort of notification system whenever the default language is updated? Not sure if this makes sense. It could be an email triggered to a mailinglist for translators or some sort of log which is available for everyone who feels like it. Till _______________________________________________ List info: http://lists.roundcube.net/dev/
