"Jason M. Felice" <[EMAIL PROTECTED]> writes:
> The reason tn5250 doesn't support iso-8859-2 is just because that's
> not what comes out the other end of the translation maps, so far as
> I can tell.
That's all I meant.
[snip]
> Hmm, I think this burns the DBCS/Unicode bridge.
I think it would just make a nice incremental improvement for
single-byte to single-byte characters sets, which is all we have now.
There's no way anyone would want to use many of the existing tables in
transmaps.h, and using appropriate mappings wouldn't need any changes
to the rest of the code. It doesn't stop us supporting DBCS and
Unicode character sets in the future.
As another example, the Hebrew CCSID 424 could translate EBCDIC 0x41
to ISO-8859-8 0xE0 (Alef), but instead it translates it to ISO-8859-1
0xC1 == � ("LATIN CAPITAL LETTER A WITH ACUTE"). The option "-m 424"
isn't useful for anyone.
The only problem I see is with some characters sets such as Cyrillic,
which might have a UNIX encoding of either ISO-8859-5 or KOI-8.
--
Carey Evans http://home.clear.net.nz/pages/c.evans/
This message was composed from the finest electrons
used by many of the world's greatest writers.
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to [EMAIL PROTECTED]
| To subscribe to this list send email to [EMAIL PROTECTED]
| To unsubscribe from this list send email to [EMAIL PROTECTED]
| Questions should be directed to the list owner/operator: [EMAIL PROTECTED]
+---
