home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!!HELSINKI,
- X-Envelope-to: NOTABENE@TAUNIVM.BITNET
- X-VMS-To: IN%"NOTABENE@TAUNIVM.BITNET"
- X-VMS-Cc: JTAKALA
- MIME-version: 1.0
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
- Message-ID: <01GT7CMM032UAH43YD@hylk.Helsinki.FI>
- Date: Wed, 6 Jan 93 15:48:16 IST
- Sender: Nota Bene List <NOTABENE@TAUNIVM.BITNET>
- From: "J-P Takala, University of Helsinki,
- Sociology" <JTAKALA@FINUHA.BITNET>
- Subject: Re: default and UU/XX format
- Newsgroups: bit.listserv.notabene
- Lines: 22
-
-
-
- Rip,
- I believe Dorothy's glosses on NBCUSTOM.SET were sent
- XXencoded, and that you should indeed have run an xxdecoder on
- them. Many programs probably know a /xx switch. When I first
- encountered the problem, I simply logged on to the nearest
- depository of public domain programs, and took the most
- promising looking ARCHIVE program that started with XX. It
- contained two programs, xxencode and xxdecode. The encoded
- messages have a header that normally reveals whether it is uu-
- or xx-encoded -- I just look at pairs of either 'u' or 'x', and
- then run either uudecode or xx_, and if that fails I run the
- other (which then fails, too).
- I have only a faint idea about the anatomy of the thing. The
- surface from my vantage point looks this: when an uuencoded
- message crosses the border between the IBM mainframe world (NB
- listserver) and the VMS/VAX world (which I get my mail to), it
- gets corrupted. XXencoded stuff seems to survive. There have
- been more learned explanation of these phenomena on this list,
- but this might help for starters.
- j-p takala
-