Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!haven!uvaarpa!mcnc!rti!xyzzy!meissner From: meissner@dg-rtp.dg.com (Michael Meissner) Newsgroups: comp.lang.c Subject: Re: need EBCDIC to ASCII function Message-ID: Date: 14 Oct 89 17:04:18 GMT References: <1060@einstein.misemi> <1989Oct4.203729.11700@utzoo.uucp> <10946@riks.csl.sony.co.jp> Sender: usenet@xyzzy.UUCP Followup-To: comp.lang.c Organization: Data General (Languages @ Research Triangle Park, NC.) Lines: 31 In-reply-to: diamond@csl.sony.co.jp's message of 6 Oct 89 10:15:50 GMT In article <10946@riks.csl.sony.co.jp> diamond@csl.sony.co.jp (Norman Diamond) writes: > In article <1989Oct4.203729.11700@utzoo.uucp> henry@utzoo.uucp > (Henry Spencer) writes: > > >You will have to be more specific. Which flavor of EBCDIC? EBCDIC is > >not a single well-defined character code, but a family of somewhat-similar > >codes. (Which is why the Unix `dd' command has two different conversions, > >plus an entry in the BUGS section discussing this problem.) ... > In fact EBCDIC is just as well-defined as ASCII. Only some IBM print > trains did not use EBCDIC. "dd" provides an alternative table so that > certain characters will print properly on those printers, but that > target code is not EBCDIC. Also IBM terminals usually did not use > EBCDIC, so the operating system had to translate to and from the > device codes. I dunno, the IBM, NCR, SAS, SDRC, and Unisys representives on the ANSI C committee seemed to bring up the point often enough that there were regional variations in EBCDIC, just like there are variations in ISO 646 (of which, ASCII is the USA varient). If anybody would know, it would be three vendors of computers that use EBCDIC, as well as one user. -- Michael Meissner, Data General. If compiles where much Uucp: ...!mcnc!rti!xyzzy!meissner faster, when would we Internet: meissner@dg-rtp.DG.COM have time for netnews?