On Sun, Oct 09, 2005 at 03:42:24PM -0700, Mark K. Kim wrote:
> There were two bigger issues, though:
> 1. ko.po was updated by someone or something, but it wasn't updated
> to the latest version of tuxpaint.pot. So I sat for half an hour
> updating ko.po to an old version of tuxpaint.pot... only to realize
> later I wasn't working on the right version. It didn't take much
> effort to adapt to the new version, but other .po files in similar
> boat may end up with an outdated translation if the translator
> doesn't update the .po file against the new tuxpaint.pot.
> 2. When ko.po was updated, some of the strings ended up getting paired
> with the wrong translations. From the looks of it, it was some
> scripted process and the program didn't match things up right... is
> my guess anyway. Didn't take much effort to fix 'em, but we may
> have some wrong translations in the .po pool and may require
> all translators to check all entries of their .po files.
Eek. Sorry, thanks for the note.
I'm currently staring at the Translation Project website, trying to figure
out how the _heck_ to get all of our latest .po's and .pot uploaded
to them. I guess I just e-mail them all to the TP Coordinator address...?
I'm sitting in the #tux4kids IRC channel on irc.freenode.net 24/7.
I might not actually be in front of my computer, but you might catch me.
I think I need to e-mail all of the past translators to have them
update their POs, too... (Not everyone is on the tuxpaint-i18n list.)