On December 22, 2010 11:25:53 pm Yuval Levy wrote: > The right way to update translations that already exist in the codebase is > `msgmerge -o merged_translation.po existing_translations.po > new_contributed_translations.po` > > First question: the above is what I understand when reading msgmerge's > manpage. It is the opposite of what is described in the translation guide. > Should the translation guide be corrected?
Thanks to Alexandre Prokoudine [0] and Lu Fang [1] for the Russian and Chinese translations in the bug tracker. I made a quick experiment: msgmerge -o ru.oldfirst.po ru.po new.ru.po msgmerge -o ru.newfirst.po new.ru.po ru.po msgfmt -c --statistics ru.newfirst.po msgfmt -c --statistics ru.oldfirst.po Same with the Chinese translation. The resulting files are of different file size and impossible to compare with traditional code inspection tools such as diff. And indeed they are completely different: ru.newfirst: 1069 translated messages, 47 fuzzy translations, 46 untranslated messages. ru.oldfirst: 982 translated messages, 108 fuzzy translations, 68 untranslated messages. similar results with the Chinese translation. This indicates that the new files should be the first argument of the msgmerge command; and that's also what the Hugin Translation Guide says. I must have misinterpreted the msgmerge man page. Yuv (one step closer to issuing the release candidate) [0] https://bugs.launchpad.net/hugin/+bug/693304 [1] https://bugs.launchpad.net/hugin/+bug/693735
signature.asc
Description: This is a digitally signed message part.
