On Sat, Feb 28, 2004 at 05:44:20PM +0100, Christian Perrier wrote: > > instead of "zh_TW". BTW, does anyone have any idea where such a > > list of languages could be kept? This looks like iso-codes of the > > like, but I have doubts, whether such an out-sourcing should be > > done, because the > No, you're right, this is the purpose of the iso_639.tab list in > iso-codes. > Your script could test for /usr/share/iso-codes/iso_639.tab and use > it if available.
Hmm. Looking into the file I see all the languages, but this list is not usable in some cases, like the mentioned zh_TW, in which I can only tell it's Chinese, but not which "flavour" it is. Should I just write something like "Chinese (TW) by <....> "? The same for Brazilian Portuguese. I could use the iso_3166_1.tab file, but it would yield something like "Chinese (Taiwan, Province of China)", but it's not how it's meant to be. Analogous for pt_BR: "Portuguese (Federative Republic of Brazil)". I'm confused ;) > Apart from this and the zh_TW issue you solved, I think the script > output is fine. However, I didn't carefully checked whether it > properly found all updated files. I think the logic is so simple, that if the translators update the PO-Revision-Date and the maintainer of the package inserts a correct revision date (both should be the case), then it will definitely work. But, like I said, the script needs testing. -- Nikolai Prokoschenko [EMAIL PROTECTED] / Jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
