> Although it would be nice for libiconv to accept the character set in a > case insensitive manner, all the installed implementations are not going > to change soon. I think it would be simpler for the Free Translation > project to have a script which checks for valid character sets in the > translations as they are checked in. For the lynx translations, at > least, we can fix those in the lynx distribution.
I would rather not use any .po files in any case which don't follow the existing standards. So Bruno's offer is either to make an incompatible extension (best ignored), or a bug-fix (would be nice ;-). -- Thomas E. Dickey <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
