[Pkg-isocodes-devel] Fw: iso_3166-1.8.pot

Fri Jan 11 21:59:28 UTC 2008

On Mon, 07 Jan 2008 16:30:41 +0100
Benno Schulenberg <coordinator at translationproject.org> wrote:

> Owwwww.  This is painful.  I haven't looked in the tarballs since I 
> asked you for a link to your SVN repo, to which you didn't answer.  
> So I never synced the iso_3166*, iso_4217 and iso_639 PO files in 
> your tarballs with those at the TP.  Only for the new iso_15924 I 
> imported all tarball PO files to the TP archives.

Hi Benno,

sorry for the delay, I've just forwarded your mail to our mailing list
and reply here.

I'm sorry to hear that. We certainly don't want to make those imports
harder than they need to be. I hope we can work out a reasonable
solution for a better synchronization.

> Now, looking in the tarball and comparing all files, I see you have 
> accepted several PO files again outside of the TP.  For example for 
> iso_15924:
> 
> -"PO-Revision-Date: 2007-09-07 21:15+0200\n"  <<<TP
> -"Last-Translator: Tobias Toedter <t.toedter at gmx.net>\n"
> +"PO-Revision-Date: 2007-12-01 14:34+0100\n"  <<<tarball
> +"Last-Translator: Christian Perrier <bubulle at debian.org>\n"
>  "Language-Team: French <debian-l10n-french at lists.debian.org>\n"
> 
> -"PO-Revision-Date: 2007-09-09 16:07+0200\n"  <<<TP
> -"Last-Translator: Tobias Toedter <t.toedter at gmx.net>\n"
> -"Language-Team: Russian\n"
> +"PO-Revision-Date: 2008-01-06 18:00+0300\n"   <<<tarball
> +"Last-Translator: Yuri Kozlov <kozlov.y at gmail.com>\n"
> +"Language-Team: Russian <debian-l10n-russian at lists.debian.org>\n"
> 
> Please don't do that.  Please urge Christian to join the TP, or 
> otherwise tell me to mark French as external (if Christian is going 
> to keep the file up to date).  Yuri already joined the TP, so I can 
> easily assign this and the other iso domains to him.

That would be good, thanks. Indeed, French is special, because
Christian does not need to translate the English texts. The ISO
standards are published both in English and French, so he just needs to
copy the relevant parts into the French .po file. Therefore, I think
that marking French as external would be a good solution.

> For iso_4217 you forgot to sync two files with those at the TP: 
> sk.po and sv.po.  Both are newer at the TP:
[...]
> Please import those two files.

Done, thanks for spotting this.

> I can go on for the other iso domains, but it seems to me that the 
> combination of the TP and the isocodes packages is a difficult one: 
> all of the iso_* subdirectories in the tarball contain some or many 
> more files than are present at the TP.  So I cannot import all of 
> those files (or I would have to create empty, pointless teams).
> 
> However, most of those extra tarball files contain just one or even 
> zero translated messages, and could in my opinion just as well be 
> deleted.
> 
> For iso_15924:
>   Not at TP: ps.po
> 1 translated message, 130 untranslated messages.
>   Not at TP: so.po
> 0 translated messages, 131 untranslated messages.
> 
> For iso_4217:
>   Not at TP: af.po
> 0 translated messages, 274 untranslated messages.
>   Not at TP: ms.po
> 1 translated message, 273 untranslated messages.
>   Not at TP: mt.po
> 1 translated message, 273 untranslated messages.
>   Not at TP: pa.po
> 1 translated message, 273 untranslated messages.
> 
> For iso_639:
>   Not at TP: aa.po
> 0 translated messages, 486 untranslated messages.
>   Not at TP: bn.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: br.po
> 0 translated messages, 486 untranslated messages.
>   Not at TP: fo.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: gez.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: gv.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: haw.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: hy.po
> 1 translated message, 3 fuzzy translations, 482 untranslated 
> messages.
>   Not at TP: iu.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: ka.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: kk.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: kl.po
> 0 translated messages, 486 untranslated messages.
>   Not at TP: kn.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: kw.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: ky.po
> 0 translated messages, 1 fuzzy translation, 485 untranslated 
> messages.
>   Not at TP: om.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: pa.po
> 0 translated messages, 1 fuzzy translation, 485 untranslated 
> messages.
>   Not at TP: sa.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: sid.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: so.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: sq.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: sw.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: syr.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: te.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: ur.po
> 1 translated message, 1 fuzzy translation, 484 untranslated 
> messages.
>   Not at TP: uz.po
> 1 translated message, 485 untranslated messages.
>   Not at TP: wal.po
> 1 translated message, 485 untranslated messages.

Hm, I have to look at those more closely, but I think that you're
probably right. Most of those files have been created by Alastair, some
have been created by me. We imported available translations from the
ICU libs, so there's currently nobody caring for those "translations".
I agree that having only 1 translated message in a file is a reason for
removal. Christian, Alastair, what's your opinion on this?

> But even after deletion of all those files, several iso_639 files 
> remain that contain a substantial amount of translated strings but 
> whose team does not exist at the TP.  What to do?  I can't expect 
> you to first check the TP pages to see whether a team exists before 
> accepting a PO file directly.  What I would like you to do, though, 
> is to never accept a PO file directly any more, but always send the 
> submitter on to the TP -- to join their team, or have a new team 
> created if it doesn't exist yet.  If one or two translators who now 
> have direct SVN access don't want to use the TP, then let me know, 
> so I can mark their languages as external and remove those PO files 
> >from the TP.

Thanks for your offer. However, I can only suggest to new translators
to join the TP, I certainly cannot force them. Currently, we accept
translations from the TP, via the Debian Bug Tracking system, and per
direct write access to our SVN repository. Some people send their
translations to our mailing list.

As you can see, there are currently several different workflows
involved, and I'd like to maintain those different approaches for
translators. The main reason for the iso-codes package is to accept
translations, therefore I would not like to force translators to one
single workflow, but rather keep as many channels for collaboration
open as possible.

On the other hand, I can understand your problem and would like to find
a solution for that as well.

Could you please explain what "marking a translation as external"
means? Will those .po files be skipped during import of a new iso-codes
tarball? Or will the TP copy of those files always be overwritten by
our .po file? Will they be ignored completely (i.e. not appear on the
TP website)?

If a translation has been marked as external, is it possible to remove
that mark again, so that a new translator can use the TP, while the
former translator didn't want to? Is it possible the other way round?

Regards,
Tobias

-- 
Tobias Toedter   | God, I ask for patience -- and I want it right now!
Hamburg, Germany |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-isocodes-devel/attachments/20080111/60e723d6/attachment.pgp 