Am Donnerstag, 30. Juli 2015, 03:49:05 schrieb Carlos E. R.:
On 2015-07-30 03:26, Richard Brown wrote:
On 30 July 2015 at 06:49, Carlos E. R. <> wrote:
And factory, aka Tumbleweed, is not translated. We only translate the stable versions.
If this is a policy, I think 'we' should change it.
It is not a policy; it just is not feasible.
Some months ago, a member of the Spanish translation team invested a lot of effort in translating things on Tumbleweed, but he had to stop when he noticed that his translated texts were not appearing on TW, and we couldn't help it.
Translators can translate, but other people have to provide the translators with the texts to translate (*.pot files), and then other people have to apply those translations (*.po) back to the devel source files, and create the appropriate packages. I think that one of the complications is that bot groups (translators and developers) work on different servers (svn and git?). The details of that part are foggy to me, sorry.
This is a manual process, and I understand only one or two persons do it. Ask Karl Eichwalder for details. He needs help for handling Leap, there is currently no way to translate it, either.
But the end result is that this cycle is only done during the string freeze phase, ie, a bit before the RC, I suppose that because it is complicated and manual. There is no procedure in place for working on Tumbleweed, it would have to be automated.
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. Obviously devs can change a lot of strings, causing a large part of the translation to have to be redone. Which is why on the roadmap there was a date for "string freeze".
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. This discourages translators which avoid to work again on that bunch. It would be easier to translate those things upstream.
I hope this clarifies the situation a bit :-)
Yes, thank you. To me this seems that processes and responsibilities should be re-evaluated. As should be priorities. For instance UI-items should come first, I think. Doing the same cumbersome, time-consuming work over and over again really makes no sense. Do it once, on the last RC, and then only minor corrections. Except you get paid for it. But even then...I think this is stuff that could be done by, well, computers? ;) Regards! And hats off to the translators! Rainer Fiebig -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org