On Wednesday 09 December 2009, Chris Cannam wrote: > I'm never quite clear on this one -- does adding a string that is the > same as an existing string, and for which the same translation is > guaranteed to be correct (because it has the same purpose in the same > context) violate a string freeze?
I'd say so, yes, because the idea of a string freeze is that if you get to 100% complete today, your work is done, and you don't have to worry about your translation again until next time. Even if the "same-text heuristic" provides these translations (this is not guaranteed) they will still require the attention of a translator, as they will be marked "unfinished." I think KDE/gettext/.po worked differently, weighted in favor of "fuzzy" translations that were often quite wrong, and trying to fill in as many translations as possible. The new stuff expects you to use Linguist and the "phrases and guesses" window to pull "fuzzy" translations in for yourself manually, while the "same-text heuristic" is very strict. I would argue a little too strict. Translation contexts are annoying too. I've got a problem on the back burner where I have valid translations, and can't put them together with the GUI due to a context misunderstanding. My usual boilerplate solution to that kind of problem did not work here, and I need to investigate further. Anyway, we'll all get through it one way or another. -- D. Michael McIntyre ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
