home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!stanford.edu!unixhub!fnnews.fnal.gov!overload.lbl.gov!dog.ee.lbl.gov!network.ucsd.edu!sdd.hp.com!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!wupost!howland.reston.ans.net!paladin.american.edu!auvm!SIVM.BITNET!NASSH100
- Message-ID: <NOTABENE%92121318273354@TAUNIVM>
- Date: Sun, 13 Dec 92 11:24:44 EST
- Sender: Nota Bene List <NOTABENE@TAUNIVM.BITNET>
- Comments: Converted from PROFS to RFC822 format by PUMP V2.2
- From: Allan Needell <NASSH100@SIVM.BITNET>
- Subject: an xxdecode trick
- Newsgroups: bit.listserv.notabene
- Lines: 27
-
- From: Allan Needell
-
- For those who have been frustrated trying to decode an xxencoded file
- transmitted in an email message, perhaps my experience will be helpful.
-
- Several times I have tried to decode downloaded xxencoded files only to get
- the dreaded "invalid character in line x" message. I'm familiar with that from
- uuencoded email messages, which I cannot decode because my system maps both
- right and left handed square brackets to the same | (vertical hyphens)
- character. But xxencoding uses only lower ascii characters and they are mapped
- correctly, hence the frustration. What I found out awhile ago and just
- reminded myself, is that my system (or something else) introduces an extra
- space following each carriage return on my downloaded email files. The space
- is the above mentioned "invalid character.
-
- For me to xxdecode an email message (I don't know if Ken or others have the
- same experience) I must globally delete the spaces following carriage returns
- in the downloaded files. Once done, the -x switch of the uudecode program
- (actually, if the file ends in the xxe extension the -x switch is invoked
- automatically) works every time.
-
- I hope someone finds this trick useful.
-
- Allan Needell
- National Air & Space Museum
- Smithsonian Institution
- Washington, DC 20560 (BITNET: NASSH100@SIVM)
-