Xref: utzoo comp.unix.questions:25123 comp.unix.ultrix:4384
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!snorkelwacker!ira.uka.de!fauern!tumuc!guug!ecrc!dave
From: dave@ecrc.de (Dave Morton)
Newsgroups: comp.unix.questions,comp.unix.ultrix
Subject: Re: EBCDIC to ASCII conversion under ULTRIX
Message-ID: <1001@ecrc.de>
Date: 30 Aug 90 14:21:41 GMT
References: <90240.091342HASKINS@MAINE.BITNET> <1694@quando.quantum.de> <26264@mimsy.umd.edu>
Sender: news@ecrc.de
Reply-To: dave@ecrc.de (Dave Morton)
Organization: ecrc
Lines: 18

In article <26264@mimsy.umd.edu>, chris@mimsy.umd.edu (Chris Torek) writes:
|>>In article <90240.091342HASKINS@MAINE.BITNET> HASKINS@MAINE.BITNET
|> (Robert D. Haskins) asks for EBCDIC => ASCII conversion.
|>
|>So, the first problem with EBCDIC to anything conversion is to figure out
|>exactly which EBCDIC is being used. . . .
|>-----
|>% Actually, I am not sure what usually maps to what, but the characters []
|>  {} \ and ^ are the biggest trouble spots.

Yes indeed. It's even worse. I think they also have country specific
EBCDIC codes. I ran into this problem years ago with a System 34 here
in Germany.
                         
Dave Morton, 
European Computer Industry Research Centre      Tel. + (49) 89-92699-139
Arabellastr 17, 8000 Munich 81. West Germany.	Fax. + (49) 89-92699-170
dave@ecrc.de