-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-07-30 16:24, Karl Ove Hufthammer wrote:
Carlos E. R. wrote:
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.
Well, lokalize, being a KDE program, is very well suited to the directory structure and procedure organization used by KDE, but apparently not so well to ours. Or at least, I haven't managed to do it well. We do have an svn server, but few translators use it. Many use an intermediate platform, vertaal, that is used mostly for organization (who translates what and when). It is this platform which emails the translator assigned to a file that it needs work. The details of this depends on each language team.
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?
The devs are on a different server, git, I think. I guess there is not a single directory that has all the catalogs, but probably many, which is why they have to be collected by people for submission. This is a part of the process I don't see, so I don't know how exactly it works. This is not unique to openSUSE. The Translation Project is also convoluted: translators are told of pending work by email, retrieve the file via http download, then submit back via email. On other projects I participate (xine), I have to download the sources from packman, translate, then upload to a paste site that I can find (google drive, for instance), then post a link in an email to their mail list so that the devs them pick it. Convolution seems to be the norm; only some projects, like KDE, have it very well organized :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlW6N7cACgkQja8UbcUWM1whjQD+JVKYz2Fw+5LTq79oivoNwJPy SxJS9037ZHPRo/rP88IA/Rnu4VXZhnxo2pokhXy7kfWbofwltAjSZR+QmYMp7L8/ =kjRx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org