Carlos E. R. wrote:
On 2015-07-30 15:23, Karl Ove Hufthammer wrote:
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.)
Yes, it is the same. The translator, a human, has to visually inspect both the new and the old strings, notice what is different, then apply changes to the translated strings.
It can be a comma, a spell correction in a word, a change of order in words, something subtle that provokes an important change on the target language...
For this he needs to be told that there are changes, download the file, open the editor (lokalize, probably), perhaps load the old and the current versions, save, upload...
Hm. I have started translating for openSUSE, but have more experience with KDE. There we don’t have to be told there are changes, as there are *always* changes (i.e., daily). :) And for downloading the files, we only have to run ‘svn up’ to fetch all updated files. Using the project view in Lokalize, we can easily see which files have new or changed string (and can sort the files by the number of untranslated or changed strings). And the coloured diff in Lokalize makes it extremely fast and easy to see what parts of the English strings have changed (this is a godsend for multiparagraph strings!), and to update the translation accordingly. It’s both fast and efficient.
Plus other people have to retrieve the .pots, and after translation, submit the .pos to the devs. Typically they wait to do this till they think that all the translators have finished.
I didn’t realise this. OK, this I see as a big problem. Why would the .po files have to be *submitted* to the developers? In KDE, the latest translations are *automatically* used whenever the developers decide to package the software (i.e., using build scripts). And the latest strings are automatically (daily) extracted from various applications into translation templates. No need for either the translators or the developers to worry about it at all (except when first setting up an application for translation).
Realistically, it takes days at least. Usually weeks.
What I mean is that even a minor change in the sources cause the whole process to rerun, and the current turnaround is rather weeks than days.
Hm, that’s scary, and an indication of a very bad workflow. It really should never take more than a day, and should not involve any people doing any work except just translating. That’s why we have computers! -- 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