🚀 go-pugleaf

The problems with uudecode look as though they may have originated
through transfer of files across BITNET.  It is a well-known problem
(although I don't know if it's universal) that the characters ^~{} at
least get mangled going through a bitnet route, even if the sender and
receiver are ascii machines.  Thus sent ^ can become recieved
 ~, sent ~ recieved % ...  Of course, if this message has passed through
bitnet to you that won't make much sense!  The characters that I know
cause trouble are uparrow/caret, tilde and curly brackets.  You cannot
undo the transformation automatically since you don't know if % was sent
as such or sent as tilde.  Moral -- exchange such files via internet or
uucp.  If anyone out there has the clout to persuade the bitnet
authorities to sort this out, please do so.  It plays havoc with
resaerchers trying to exchange TeX and PostScript if nothing else.

--------------------------------------------------------------------
Snail mail:                 |   JANET: love@uk.ac.dl
Dr. D. Love,                |   BIT/INTERNET: love@dl.ac.uk
SERC Daresbury Laboratory,  |   UUCP: ...!ukc!daresbury!love
Warrington WA4 4AD,         |   alternative BITNET: love%dl@ukacrl
UK               |  alternative ARPA: love%uk.ac.dl@nss.cs.ucl.ac.uk
 'Phone: (+44/0)925 603479, Telex: ...925 629609, FAX: ...925 603173