Alberto Passalacqua <alberto.passalacqua@tin.it> writes:
A simple solution to this is to release a file for translations when it's close to its final state.
Yes, but others prefer to have files available as early as possible. That's why we have the "official" translation rounds plus unofficial "pre-rounds".
However, I'm not complaining about necessary corrections but about continuous and unnecessary, mainly cosmetic or formal, changes to strings.
Those changes were only allowed (and announced in advance) for the package management stack (zypper, etc.). Sometimes those minor changes slip in while developers are fixing a serious bug -- that's kind of annoying for the translators but hopefully tolerable.
Probably a dedicated (one week?) translation period close to the RC1 or final release would improve things, but I think it would be interesting to read other translators' opinion.
RC1 is too late--if you'd miss that date, there would not be a second chance. The last beta is actually already rather late, because there are several hops involved until translations are on the installation media. Ladislav has some ideas how we could automate this step more, but writing and testing the scripts takes time, In theory, that's easy: just 'cp', 'tar', and submit the package. But in practice we probably must run several checks on the results; for example, only propose the package for submisssion to the build system if be have better translations. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org