Hello, during the last days, we (as in: the usual people in #apparmor) discovered that the r1225 translation update introduced _lots_ of mistranslations in various languages, even for texts that had correct translations before. Also, most of the changes I commited for de.po recently fixed things that were introduced in r1225.
Therefore I propose to completely [1] revert r1225 in trunk and also in the 2.8 branch. Note that r1225 is a commit from 2009, so it's likely that we'll get some merge conflicts. We can easily "solve" conflicts by removing the translated text so that translators get a second chance. The alternative is to mark _all_ texts in _all_ languages as fuzzy, so that translators see them as "please check this". The disadvantages of this way are - we keep the mistranslations until translators have checked the translations - not the best idea because some translations are really bad (and I can only judge on en_* and de - maybe the other languages are even more funny[tm]) - it's probably more work for translators than re-translating a few texts that are a victim of revert/merge conflicts The only advantage of marking everything as fuzzy is that we'll get proofreading for all texts which might also catch mistranslations from other commits. Opinions? Objections? (if you want to see the patch for this proposal: bzr diff -r1224..1225, then swap + and -) Regards, Christian Boltz [1] except de.po because I fixed it already -- Zwar sind CSS-Bugs kein Alleinstellungsmerkmal des Internet Explorers, jedoch beansprucht Microsoft seit vielen Jahren die Marktführerschaft. [Dirk Jesse auf http://www.highresolution.info/spotlight/entry/was_sie_ueber_css-frameworks_wissen_sollten/] -- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
