Re: Apple IIe TCP-IP w/ LANceGS Card

[Jalapeno <jalapeno1@mac.com>]

In article <BunHb.24394$J77.18731@fed1read07>,
 salfter@salfter.dyndns.org (Scott Alfter) wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> In article <NoEmail-2612030813280001@h24-77-190-53.wp.shawcable.net>,
> copper wire <NoEmail@NoEmail.NoNet> wrote:
> >In article <TIadnQfaevQLe3aiRVn-hg@comcast.com>, "Bill Garber"
> ><willy46pa@comcast.net> wrote:
> >> As you can see from the "//e" in the above paragraph=20
> >> that all is fixed. My newsreader is not as "broken"=20
> >> as it was. As many different programs as I have tried,=20
> >> I still find OE to be the best for me, even with all=20
> >> of it's idiosyncrecies. Hyperlinks work in text only=20
> >> mode and that is a plus for me.=20
> >
> >Excellent. Now would you mind turning off the feature that always adds the
> >"=20" at the end of each line in all of your posts? It's a real pain to
> >read. I suspect it would be a setting related to either showing all
> >carraige returns/line feeds or something to do with HTML'izing the text or
> >possibly both.
> 
> You see it because your newsreader doesn't handle the quoted-printable
> content transfer encoding.  Even trn handles quoted-printable, and it's a
> relatively old newsreader.  (trn 4.0 was released sometime in 1995, and the
> most recent patch for that version is from April 2001.) Quoted-printable was
> defined in RFC 1521 (MIME Part I), issued in September 1993.  A newsreader
> that still doesn't handle it more than ten years later is beyond obsolete.
> 
> (That said, I suspect that changing the default character encoding in
> Lookout Express from Windows-1252 (a non-standard character encoding) to
> either us-ascii or iso8859-1 might make it go away.  I haven't used it in
> years, though, and don't have it set up on any of my machines, or I'd test
> it myself and see if it made a difference.)
> 

RFC 1521 aside (and it really is irrelevent in this case as MIME is 
defined for email and the web, but not for usenet, which is a subset of 
Internet message protocols), the X- prefix in the header makes it a user 
defined extension to rfc 822. Newsreaders are not required to interpret 
extensions to the 822 standard (little 's' standard, not big 'S' 
standard). The greatest common denominator for all news readers is plain 
text (which includes readers used by the blind). MIME adds nothing to 
the content of a usenet article. I should be able to use an ascii dumb 
terminal to read usenet articles.

Windows-1252 is a registered character set. But not for usenet. It being 
a code page that is an 8 bit ascii extension. That is why OE is using 
MIME instead of plain text. ASCII, as we all know, is a 7 bit character 
set. Windows-1252 is not.

Usenet was set up as a means for disparate groups to communicate. When a 
usenet product impedes that communication (no matter how small the 
impediment) the client creating the impediment should adjust. That is my 
opinion.