Re: lynx-dev to uuencode or not to uuencode

[dickey]

> 
> David Combs wrote: 
> >  
> > What's so bad about uudecode and gzcat? 
>  
> Uuencoding is broken by design, in my opinion.  It uses unsafe 
> characters.  There are multiple incompatible encoders and decoders. 
> A given uudecode may be picky about whether spaces are preserved 
> at line ending - just the sort of problem encoding is supposed to 
> remove!  I've had far more problems with uuencoded mails than with 
> unencoded ones. 

I've heard of people running into problems with uuencode, but so far the
only corrupt ones I've received have been "fixed" by a mime wrapper.
  
> Another point is the convenience of scanning a patch right in the 
> mailbox, to get an idea what it's about, without any external 
> incantations or special setup.  (Please don't send messages now 
> that _your_ mail reader does that automatically, it doesn't apply 
> for everyone.) 
  
sure (no problem, as long as we don't get broken lines).

I've had no problems with your patches (so your mailer works fine).
Some of the others I see are puzzling (how'd it get that way..)

>    Klaus 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey