Alberto, there are different things to translate: Those on the media and those on some servers: Release Notes and the community distros strings are available online The Release Notes will be changed also after the GA date. Therefore we can translate them at later times as well.
A simple solution to this is to release a file for translations when it's close to its final state. However, I'm not complaining about necessary corrections but about continuous and unnecessary, mainly cosmetic or formal, changes to strings. Often sentences are changed just adding a (.), a \n, a space or reformulated to say the same things.
The problem is not translation - the problem lies in development where some changes are really needed.
As said, there's no problem in this case. :-)
I agree we should strive to get everything out early - in an optimal world, you only translate after all the testing is done. But we're not there ;-(
I'm not really asking for this, but just for a better planning of translation work, which, in my opinion can be done in parallel with development only for the parts which are not changing quickly, while for the rest, which is a reduced set of .po files, it should be postponed. 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. With kind regards, Alberto --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org