2007/2/15, Pierre Schmitz <pierre@archlinux.de>:
Am Donnerstag, 15. Februar 2007 15:39:42 schrieb Dan McGee:
When you submit an updated translation, be sure to run it against an up-to-date pot file first just to make sure everything lines up and you haven't missed any new messages. I've been doing this before I submit just to make sure but it will help catch untranslated messages earlier in the process. We try not to change the English text if it doesn't need to be, but every once in a while it gets modified. Here are the steps, in the respective po directories and using either libalpm/pacman where indicated: make libalpm.pot-update (or make pacman.pot-update) make <your language>.po-update
These are safe operations, no existing translations will be lost unless they are no longer necessary (for example, a string is removed). Thanks again guys for your quick work!
How often should we synchronize our translation to cvs and send you updated files? Perhaps it would be a good idea to introduce a kind of "freeze" date after which no string were changed/added.
There can be also some notice posted like "description of makepkg option ---xyz changed, please update translations" before entering "freeze" date, so translators doesn't need to check everything each time. Opinions? -- Roman Kyrylych (Роман Кирилич)