Fwd: Readable Email

Got the following response to my "Readable Email" email, from someone
who didn't want to tell me who he really was.  Is it a valid
criticism?  I understand the encoding issue, but I haven't had a
problem with it in any of my (GUI) email clients.  The email shows up
okay on the three public mailing list archives that have the message. 
I can't reproduce the problem.  Can someone enlighten me?  Mystery-man
maybe?  Depending on the extent of systems that can't handle UTF-8,
this is an issue I'd like to address.

-todd


On Mon, 14 Feb 2005 23:22:38 -0800 (PST), Denny Crane
<anonymous-7sGlIlNGn3Vnh45NjJeCDQEDlBtz9cLLnrOTo9+9Zeg@public.gmane.org> wrote:
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bitIn message
> <e1d8c65205021309552d8034c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>, Todd Walton
> <[email protected]> wrote:
> >The active community of Freenet developers is top-notch with respect
> >to this issue, with a few notable exceptions.
> >
> >from "How To Ask Questions The Smart Way"
> >http://www.catb.org/~esr/faqs/smart-questions.html :
> >
> >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> >Write in clear, grammatical, correctly-spelled language
> >
> 
> [snip]
> 
> >Spell, punctuate, and capitalize correctly. Don't confuse "its" with
> >"it's", "loose" with "lose", or "discrete" with "discreet". Don't TYPE
> >IN ALL CAPS, this is read as shouting and considered rude. (All-smalls
> >is only slightly less annoying, as it's difficult to read. Alan Cox
> >can get away with it, but you can't.)
> >
> >More generally, if you write like a semi-literate boob you will very
> >likely be ignored. Writing like a l33t script kiddie hax0r is the
> >absolute kiss of death and guarantees you will receive nothing but
> >stony silence (or, at best, a heaping helping of scorn and sarcasm) in
> >return.
> >
> 
> Good advice.  I would add one suggestions.
> 
> Set your mail client to "Plain Text Only"
> 
> This is often reflected in message headers by something like:
> 
> Content-Type: text/plain;
>   charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> whereas <e1d8c65205021309552d8034c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> for example had the
> following:
> 
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> 
> which caused
> 
> stiff or formal - in fact
> 
> to be rendered:
> 
> stiff or formal =E2=80=94 in fact
> 
> and / or things like
> 
> =3D
> 
> scattered though the text, thus making it hard to read.
> 
> --
> The preceding is just my opinion only.  Your Mileage May Vary, Slipery when
> wet, Refrigerate after opening, People other than me are not required to
> like what I say.
> 
> "Cuckoo for Coco Puffs"
> 
>
_______________________________________________
chat mailing list
[email protected]
Archived: http://news.gmane.org/gmane.network.freenet.general
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/chat
Or mailto:[email protected]?subject=unsubscribe