Re: lynx-dev address@hidden: Re: new version of FR.PO][PATCH]

[Leonid Pauzner]

21-Jan-2003 08:11 Doug Kaufman wrote:
>> only a DOS issue?

> determining the necessary conversions. At least in the dos port of GNU
> libiconv version 1.7 (latest is 1.8), the names of the character sets
> appear to be case sensitive, and the character set "iso-8859-1" is not
> recognized (although "ISO-8859-1" is). I think that this is true for
> all platforms that run the standalone libiconv.

I think uppercasing charset in lynx *.po files is not a good idea
since new versions from the Translation Project will have mixed cases.

Instead, it would be nice to add few lines to DOS section of lynx
INSTALLATION file, with a patch to libiconv and/or a simple awk sctipt
to run upon po/ directory in case of problem, like we have with PDCurses.
(It is interesting that nobody report the problem for years).

grep "text/plain; charset=" *

ca.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
cs.po:"Content-Type: text/plain; charset=ISO-8859-2\n"
da.po:"Content-Type: text/plain; charset=iso-8859-1\n"
de.po:"Content-Type: text/plain; charset=iso-8859-1\n"
et.po:"Content-Type: text/plain; charset=iso-8859-15\n"
fr.po:"Content-Type: text/plain; charset=iso-8859-1\n"
hu.po:"Content-Type: text/plain; charset=ISO-8859-2\n"
it.po:"Content-Type: text/plain; charset=iso-8859-1\n"
ja.po:"Content-Type: text/plain; charset=euc-jp\n"
lynx.pot:"Content-Type: text/plain; charset=CHARSET\n"
nl.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
pt_br.po:"Content-Type: text/plain; charset=ISO-8859-1\n"
ru.po:"Content-Type: text/plain; charset=koi8-r\n"
sl.po:"Content-Type: text/plain; charset=iso-8859-2\n"
sv.po:"Content-Type: text/plain; charset=iso-8859-1\n"
tr.po:"Content-Type: text/plain; charset=ISO-8859-9\n"
zh_tw.po:"Content-Type: text/plain; charset=Big5\n"



; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden