Xref: utzoo comp.unix.misc:427 comp.lang.c:33176 Newsgroups: comp.unix.misc,comp.lang.c Path: utzoo!henry From: henry@zoo.toronto.edu (Henry Spencer) Subject: Re: EBCDIC <--> ASCII conversion Message-ID: <1990Oct26.162622.28024@zoo.toronto.edu> Organization: U of Toronto Zoology References: <1756@dinl.mmc.UUCP> <661@modus.sublink.ORG> <831@compnect.UUCP> <1990Oct25.140442@devils.rice.edu> Date: Fri, 26 Oct 90 16:26:22 GMT In article <1990Oct25.140442@devils.rice.edu> schafer@devils.rice.edu (Richard A. Schafer) writes: >||> However, unlike say ISO646 or ASCII, there is no one standard >EBCDIC. >To be fair, there is no *one* standard ASCII, either, if you consider >ASCII to include any of the several European versions of ASCII... There are no, repeat *no*, European versions of ASCII. ASCII is a single precisely-specified character code with no versions or ambiguities. It is one of a family of codes derived from ISO646. There are a number of other 646-derived codes in use in Europe; they are not ASCII. It is true that the existence of a variety of 7-bit codes has turned out to be a major nuisance, which is why there has been considerable work on unified codes like ISO Latin. -- The type syntax for C is essentially | Henry Spencer at U of Toronto Zoology unparsable. --Rob Pike | henry@zoo.toronto.edu utzoo!henry