Rune Nordbøe Skillingstad <rune@skillingstad.no> writes:
Alberto Passalacqua wrote:
I don't understand these rigid constraints for translators and not for developers myself. Why is RC too late? We are discussing about changing parts, which should be a very limited subset of the .po files. So as release notes are updated when needed, the community repositories are "dynamic" (why not decide which ones to include once for all is not clear, again), why is it so difficult to eventually update other's translations? We are asked for flexibility, so the same is expected on Novell side.
Please, get real ;-) A more or less serious software bug must get fixed, the sooner the better. If a minimal amount of all messages stays untranslated, that's just a cosmetic annoyance--of course, if a major menu entry is affected, it is more cumbersome.
I'm _NOT_ thinking about bug fixes and spelling errors, but repeated "new" features, and minor changes to the pots, resulting in already translated strings to be marked as fuzzy over and over.
These things are often somehow interlinked. If we must fix bugs, we sometimes (that's an exception!) allow to slip in a low amount of spell-fixed additional messages. Because the desktop user probably does not make use of command line tools that much, it is not a big issue if some of those few messages stay untranslated. It is different with YaST and I think we did not introduce new YaST strings besides bug fixing. -- 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