Re: EBCDIC <-> ASCII translation tables

A long time ago, I wrote about ISO-8859-2:

> I tracked it down to recode itself.  It looks like RFC1345 defines
> "IBM870" differently to IBM (now) defines CCSID 870.  recode, as well
> as glibc's iconv function, are based on RFC1345; and transmaps.h in
> tn5250 is generated from recode's output.

I've come up with a new set of tables, and a Python program (that's
only a bit more complicated than it needs to be) to generate
transmaps.h from them.

Because the tables are separate, they can be updated more easily and
new character sets that recode doesn't understand can be added.

To download the Python `transmaps' and the tables I've done so far, see:

    http://home.clear.net.nz/pages/c.evans/sw/transmaps/

I think it would be a good idea for the transmaps.h generated from
this to go into tn5250, once everyone's happy with the character sets
included, since it fixes incorrect mappings in most of the character
sets.

-- 
         Carey Evans  http://home.clear.net.nz/pages/c.evans/

Prof:    So the American government went to IBM to come up with a data
         encryption standard and they came up with ...
Student: EBCDIC!"
+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---