Article View: comp.mail.misc
Article #4562Re: ASCII/EBCDIC Translation
From: Samuel Lam
Date: Sun, 13 Dec 1987 03:01
Date: Sun, 13 Dec 1987 03:01
18 lines
1344 bytes
1344 bytes
In article <425@minya.UUCP> jc@minya.UUCP (John Chambers) writes:
)It would be interesting to learn just what characters (i.e., hex values)
)can be safely transferred through ASCII/EBCDIC interfaces. An encoding
)scheme like uuencode could be written using translation tables, if there
)are 64 character codes that can be guaranteed reliable in all ASCII/EBCDIC
)interfaces.
)
)... Are there 64 codes that can be trusted to any ASCII/EBCDIC translators,
)and will come out the same when fed to any other EBCDIC/ASCII translator?
The upper *and* lower case alphabet and the digits together make up 62 of
these characters. Anyone have suggestions for the two more to go? (I think
'*' and '#', among others, could do it.)
...Sam
--
Samuel Lam <Samuel.Lam@van-bc.UUCP> or
{ihnp4!alberta,watmath,uw-beaver}!ubc-vision!van-bc!skl
Technical Details
Message-ID:
<1622@van-bc.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!uunet!van-bc!sklReferences:
<425@minya.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!van-bc!skl From: skl@van-bc.UUCP (Samuel Lam) Newsgroups: comp.mail.misc Subject: Re: ASCII/EBCDIC Translation Message-ID: <1622@van-bc.UUCP> Date: 13 Dec 87 03:01:13 GMT References: <425@minya.UUCP> Reply-To: skl@van-bc.UUCP (Samuel Lam) Organization: UBC Department of Computer Science, Vancouver, B.C., Canada Lines: 18 Keywords: ASCII EBCDIC Translation Character Code Summary: 62 characters that "should" go through ASCII/EBCDIC translation fine.