Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!sabre!gamma!ulysses!allegra!mit-eddie!husc6!bbn!uwmcsd1!ig!jade!ucbvax!decvax!decwrl!sun!quintus!jbeard
From: jbeard@quintus.UUCP
Newsgroups: comp.mail.misc
Subject: Re: ASCII/EBCDIC Translation
Summary: incompatible ascii vs ebcdic
Message-ID: <522@eden.quintus.UUCP>
Date: 11 Jan 88 18:04:37 GMT
References: <425@minya.UUCP> <1987Dec15.101835.3795@jarvis.csri.toronto.edu> <3089@dscatl.UUCP>
Organization: Quintus Computer Systems, Inc: Mountain View, Ca
Lines: 20

In article <3089@dscatl.UUCP>, lindsay@dscatl.UUCP (Lindsay Cleveland) writes:
> I've needed to do ASCII <-> EBCDIC conversion, I've found that the
> "dd" command works just fine, ....

However EBCDIC contains a cent-sign and a PL/1 NOT and ASCII characters like
	[]{}`\~^
are often mis-translated.

most offensive, is the incompatible representations of \n (newline), which has
a history of:

	cr, lf pair for old tty-35 devices

and a later development of

	nl

DD typically maps \n to the lf, which isn't correct.

Posting C source to an EBCDIC environment can be fun ...