Article View: comp.lang.postscript
Article #2523Hex and <>
From: Mark Martino
Date: Thu, 12 Jul 1990 15:20
Date: Thu, 12 Jul 1990 15:20
10 lines
1009 bytes
1009 bytes
Thanks to Woody for posting the eexec stuff. I'm still rooting through it, but it looks like it will help. We found that the interpreter we purchased to port to our printer, the MT906 PS, had the same problem that Woody described concerning handling cr/lf in hex data. We found that our problem was at a very low level, not even in the interpreter actually. We corrected the problem by modifying how we handled cr and lf in the character input routine. I can't speak for other hardware configurations, but that was where our problem was.
Technical Details
Message-ID:
<1224@mtk.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!mit-eddie!uw-beaver!sumax!polari!thebes!mtk!marmarShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!mit-eddie!uw-beaver!sumax!polari!thebes!mtk!marmar From: marmar@mtk.UUCP (Mark Martino) Newsgroups: comp.lang.postscript Subject: Hex and <> Summary: How they interact with cr/lf Message-ID: <1224@mtk.UUCP> Date: 12 Jul 90 15:20:07 GMT Reply-To: marmar@mtk.UUCP (Mark Martino) Distribution: usa Organization: Mannesmann Tally, Kent, WA 98032 Lines: 10