[Pkg-isocodes-devel] Submit pot file to TP before release?

Alastair McKinstry mckinstry at computer.org
Tue Oct 17 17:32:48 UTC 2006


Christian Perrier wrote:
> Quoting Abel Cheung (abelcheung at gmail.com):
>   
>> Hi,
>>
>> Currently it seems that translation templates are submitted to TP
>> _only_ after the tarballs are made. That means people submitting
>> translation through TP will always be at least one release behind
>> the newest one. How about sending .pot file to TP people after
>> string freeze (if there is one) but before releasing tarball, so that
>> translators can update iso-codes in time through TP as well?
>>     
>
>
> That would be fair with TP translators, yes.
>
> Actually, we do set string freezes explicitely only for ISO-3166
> because these translations are directly used for Debian Installer
> where we benefit from completeness of translation of country names
> directly, for languages supported in Debian Installer.
>
> But, for sure, that's a little unfair to other translators.
>
> I'm not deeply familiar with TP process, though. Tobias?
>
>
>   
I think its worth doing this before any release that changes the list of
entries;
normally I've labelled these as the 'upstream' release.  We would do regular
debian releases that just include additional translations; no need to
ping the
translators if the files to be translated have not changed.

e.g. the next planned release (21st) is a 'debian' release; no need to
upload to
TP in advance of it.

Regards
Alastair

> ------------------------------------------------------------------------
>
> _______________________________________________
> Pkg-isocodes-devel mailing list
> Pkg-isocodes-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-isocodes-devel
>   




More information about the Pkg-isocodes-devel mailing list