FISHER@RPIECS.BITNET ("John S. Fisher") (12/22/89)
In response to this long debate about the various flavors of uuencode, I've
been researching the whole problem as best I can. Not being a "Unix-person"
nor in close touch with the Unix community, this has taken longer than it
might otherwise had. At any rate, the result is the following announcement.
Effective immediately:
(1) The server at RPIECS uses the grave-accent substitute for blank in
its uuencoder. Since this eliminates the trailing blank truncation
problem, the trailing M character is removed. I believe that the
uuencoding variant now in use conforms to the officially recognized
standard method.
(2) The option OLDUUE is available on the /PDGET command to explicitly
request the trailing-M form for those that really need it. The
speculation is that no-one will, so this option may be removed in
the future.
(3) As an alternate to uuencoding, the so-called xxencoding method can be
requested by specifying XXENCODE as an option on the /PDGET command.
(4) The PDGET HELP file will be updated to reflect the changes.
The user-visible change here is that uuencoded files, implicitly or explicitly
requested, are now being sent in the newer format. (Please note that
checksumming is *not* included. I have been informed that this is not (yet?)
an official standard variant.) I hope this is good news for some and no news
for most of you.
On the side of bad news: In the process of making this change today, three
user requests for uuencoded data slipped in during testing. They were
incorrectly sent out as xxencoded files. My apologies to the users affected by
this error.
I am now in the process of packaging the server changes to forward to NDSUVM1.
I suspect the people there will be making the same changes in short order, but
the actual schedule is for them to determine.
/JSFisherroy@comcon.UUCP (Roy M. Silvernail) (12/23/89)
In article <KPETERSEN.12551937699.BABYL@WSMR-SIMTEL20.ARMY.MIL>, FISHER@RPIECS.BITNET ("John S. Fisher") writes: > (3) As an alternate to uuencoding, the so-called xxencoding method can be > requested by specifying XXENCODE as an option on the /PDGET command. I have heard of xxencode, and even have a version of it for my PC. (I'm a rabid collector of encoders and archivers :-) I have never seen it used, though. Does it have advantages/disadvantages over UUencode? -- _R_o_y _M_. _S_i_l_v_e_r_n_a_i_l | UUCP: uunet!comcon!roy | "Every race must arrive at this [ah, but it's my account... of course I opine!] point in its history" SnailMail: P.O. Box 210856, Anchorage, | ........Mr. Slippery Alaska, 99521-0856, U.S.A., Earth, etc.| <Ono-Sendai: the right choice!>