Carlos E. R. wrote:
Notice also that, even if that can be automated, it is big effort for translators to work on software that is changing from day to day. It takes time to translate (we are note professionals, yet we take pride and effort on it), and then a week later a dev changes a single comma on a string, and it is null. Has to be translated again.
As a translator of many free software applications, I’m not sure I understand this correctly. What I’m used to is this: 1. The translator translates the string. 2. The developer changes a single comma in the original (English) string. 3. The translation is automatically marked as ‘fuzzy’, which means that it’s not used, but still available. The original string is kept. In the translation editor the translator can see the new English string and which changes have been done (this is typically shown as coloured ‘diff’ output, showing which characters have been removed and added in the English string). 4. The translator updates the translation, by just removing the ‘fuzzy’ status (if the translation don’t need any changes), or by editing the translation (e.g., adding/removing the missing/extraneous comma). So for small changes in the English strings, it’s very quick to keep the translations updated. This is a very efficient way to work for both translators and developers. Does the translation system in openSUSE differ from this workflow? (It does use standard .po files, so I would expect it not to.)
About menus, Yamaban explained the issue, which is another complication on top of the above, general issue. The menus, the software description package, contains several thousand of entries, and every release has to be done again almost from scratch, previous work is lost.
-- Karl Ove Hufthammer E-mail: karl@huftis.org Jabber: huftis@jabber.no -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org