Re: asdbget: character set

[Carey Evans <c.evans@xxxxxxxxxxxx>]

"Jason M. Felice" <jasonf@shell.nacs.net> writes:

> Maybe next release.  Certainly the next release will put the character
> encoding in the XML file, but this means we have to add this info to the
> transmaps table.  (Not a big deal)  I also have to wonder about whether
> you can encode XML in weird character sets like this - like ones that don't
> have enough of the characters needed for XML markup.  Do we have to do UTF8
> here?  Or do all the iso-8859-* fonts have ascii as the lower 127 characters?

The default encoding of XML when the file starts with '<', '?', 'x',
... is UTF-8.  Every XML parser _must_ be able to handle UTF-8 and
UTF-16 encodings.  See section 4.3.3 in the XML 1.0 standard.

You can also declare the whole file as being in one of ISO-8859-x, or
one of three Japanese encodings.  I don't know which of these
corresponds to the JIS_X0201 that recode knows about.

All the ISO-8859-x encodings have the first 161 characters in common,
as far as I can tell.  JIS_X0201 has a couple of characters in other
places.  An easy way to get a table for each character set is
`recode -lf iso-8859-2', etc.

All the single-byte EBCDIC encodings have a set of invariant
characters, too.  It covers A-Z, a-z, 0-9, and some punctuation like
@(),_-*, so it should always be possible to parse the DSPFFD output
unless IBM change the positions of the fields.

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

"*South Park* is another movie straight from the smoking pits of Hell."
                       - http://www.capalert.com/capreports/southpark.htm
+---
| 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
+---