Am Montag 17 September 2007 schrieb Alberto Passalacqua:
Hello, it's the first time I cooperate with the translation of a distribution, so I'm not expert in the field. However, the planning of translations seems lacking to me.
During the official translation period we had changes to .po files which made us translate or check strings again due to unexpected changes, with a significant lack of time for translators.
After string freeze, I may understand the changes to release-notes, but we had changes mainly to zypper, zypp, and, in minor measure to other .po files.
Now an almost completely untranslated .po file appears, while feature and string freezes are passed.
Why isn't a better planning in translation done to avoid repetitive work? It would be enough to set a hard string freeze one month or so before the translation deadline and to make developers absolutely respect it (27 strings changed in release notes!) so to give time to translators to translate strings and proofread only once.
I hope this will be seriously considered for the next openSUSE release.
The release notes is the place where we put last minute changes. So this will never be different - which is also the reason we download them before display. The PO file in question though isn't bound to the 10.3 release per se. The list of community repositories will be dynamic through the life cycle of the release, so it will change any time and translations will be pulled in from trunk. New repositories will appear first in english and will then be updated with a translation. This is similiar to the wiki, just that we decided to go the PO way, so we don't have to maintain different repositories for different languages. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org