FreeTDS Development Group

[Steve Langasek <vorlon AT netexpress.net>]

On Tue, Sep 03, 2002 at 06:36:01AM -0700, James K. Lowden wrote:

> > Secondly, if we are going to support
> > character sets in which 0-9 and . are not in
> > their ascii positions the convert code will
> > have to know whether to call iconv or not. I
> > don't see anyway around this....open to
> > suggestions though.

> I've been dissuading people from testing against 30 when they mean '0'
> based on mesozoic habits of portability.  

> Assertion: Every character set iconv can deal with has the digits
> '0'..'9' in sequential order.  Same goes for 'A'..'F'.  (I bet everyone
> the world over writes hex the same way.)  The only exception I've ever
> seen is EBCDIC IIRC, and on the iconv FAQ the EBCDIC question has a
> one-word answer, "No!"

Further assertion: all national language character sets in current use
on either Unix or Windows platforms are codepoint compatible with ASCII. 
With the exception of widechar encodings (UCS-2 and UCS-4), they are also
byte-compatible with ASCII.

Steve Langasek
postmodern programmer

Attachment: pgp50A0In5DI8.pgp
Description: PGP signature