Re: [pacman-dev] Updated translations
On 2/15/07, Douglas Soares de Andrade <douglas@paradigma.com.br> wrote:
Em Quarta 14 Fevereiro 2007, Giovanni Scafora escreveu:
2007/2/14, Dan McGee <dpmcgee@gmail.com>:
Done.
Excuse me, can you re-update these .po files? Thanks again.
Hey, we have an update too. Can it be updated ?
Translators, 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! -Dan
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. -- http://www.archlinux.de
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 (Роман Кирилич)
On 2/15/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2007/2/15, Pierre Schmitz <pierre@archlinux.de>:
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?
Both of these are good ideas, and why don't we try to do that from now on. Lets say the freeze date for strings for pacman 3.0 is now. However, at times, an original string was not clear, so it needs updating. I think a complete freeze would not make sense in this case, as the released product would have bad text. But we can keep string changes to a minimum, and when one is made note it in the commit message. I know I changed one this morning, but your translations may have already been more accurate than the original English wording - the text for 'using default "C" locale'. Is this acceptable to everyone? -Dan
Am Donnerstag, 15. Februar 2007 16:04:25 schrieb Pierre Schmitz:
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.
OK, synced my po-files with pacman-cvs: (no big changes) http://svn.laber-land.de/pacman-de/trunk/lib/libalpm/po/de.po http://svn.laber-land.de/pacman-de/trunk/src/pacman/po/de.po -- http://www.archlinux.de
participants (3)
-
Dan McGee
-
Pierre Schmitz
-
Roman Kyrylych