(CC to the OP) Hi everyone :)I've kept the entire text of the OP, since it's all relevant to my reply.
On 08/09/2009, at 4:30 AM, Zack Weinberg wrote:
[Resending - seems to have gotten dropped last time.] Dear Debian I18N people, I would like to know if some of you would be interested in translatingmonotone's diagnostic messages (that is, the upstream POT file). Thereare already some translations, but upstream lacks translator manpower.I am particularly interested in help with existing incomplete translations:language translated fuzzy untranslated ----------------------------------------------------- de 1307 2 8 es 1255 32 30 fr 786 241 290 it 1165 21 131 ja 564 325 428 pt_BR 719 250 348 sv 1279 14 24 and in languages where the debconf templates are translated, but the program messages are not: cs, nl, and ru. However, translations for any language are much appreciated. Advice on whether the existing pt_BR (Brazilian Portuguese) translation could be promoted to a generic Portuguese translation would also be appreciated. As I'm soliciting help with upstream translation, there is no deadline. However, a new upstream release is likely to happen in a couple of weeks, and it would be nice to get the incomplete translations, at least, fixed up before then. Please send new or updated translations directly to me <zackw@panix.com> or to the upstream development list <monotone-devel@nongnu.org>. Please do *not* file Debian bugs for this. You can download a tarball containing the POT file and all the current PO files from <http://www.owlfolio.org/debian/monotone-po.tar.gz>. It unpacks into the current directory. Thanks in advance, zw
Just some advice on trawling for translators, Zack: we are as busy as you are, and sometimes working pan-project. We are likely to prioritize by time and efficiency.
For example, when I have some time, I always do my D-I files first, then the updated PO files directly emailed to me, then the POT files sent to this list. Everything else tends to fall off my ToDo list. I nearly didn't do your monotone file, because it wasn't attached to the email. (Fortunately, once I did start it, I was too stubborn to stop. ;) )
So it's better practice to attach the POT file to the translation- request email. You are likely to get more bites that way. ;)
You can also setup your workflow so each time you update the POT file, updated PO files are automatically generated and emailed to each of the previous translators. For Debconf files, this is done with po- debconf, but I'm not sure which package is used for program files.
Christian, what should Zack use to organize translation updates for monotone? His program doesn't seem to use the BTS, so I'm unsure how much of our i18n infrastructure he can use.
Also, Zack, if you start using the Debian BTS, that is another plus for translators, since emailing translations to the BTS, and monitoring their status there, is a key part of our workflow. When we're short of time, we tend to stick to the familiar and the effective.
Good luck. :) from Clytie Vietnamese Free Software Translation Team