In article . org,
Kristian M Zoerhoff wrote:

On 2010-12-09, Michael Press wrote:
In article . org,
Kristian M Zoerhoff wrote:

On 2010-12-09, T?m Sherm?n? ?_? "" wrote:
On 12/8/2010 8:22 AM, Duane H?bert wrote:
On 12/7/2010 8:13 PM, T?m Sherm?n? ?_? wrote:
On 12/7/2010 8:22 AM, Duane H?bert wrote:
On 12/6/2010 9:21 PM, T?m Sherm?n? ?_? wrote:
On 12/6/2010 10:08 AM, Duane H?bert wrote:

At home I use Outlook Express for a news reader.[...]

Bill Gates holding a gun to your head?


Huh?

Why would anyone use a Micro$oft product when better, free alternatives
are available? (Assuming that they are given a choice.)


I haven't got around to installing TBird at home. Last year when I
tried it, it sucked too much. The current version seems ok - I'm using
it at work.

The "Huh?" was more about you telling me to use a newsreader that will
let me respond to your posts in lieu of you not doing funny things to
your header.

So huh?

My header is UTF-8 compliant.

Alas, usenet is not. It's a 7-bit medium.

All headers must be ASCII. Header titles
must be exactly as prescribed. HOWEVER... there are
means to communicate and render glyphs outside
ASCII. You have some reading to do, but I
promise it is rewarding reading.

http://en.wikipedia.org/wiki/MIME
http://tools.ietf.org/html/rfc2047

I'm aware of how MIME works. It doesn't change the underlying foundation of
Usenet, it just makes it possible to piggyback non-ASCII content onto an
ASCII medium of transport.

Not a 7-bit medium as you assert.
Network News Transfer Protocol, rfc 3977, 3.1.1 reads

Note that texts using an encoding (such as UTF-16 or UTF-32) that may
contain the octets NUL, LF, or CR other than a CRLF pair cannot be
reliably conveyed in the above format (that is, they violate the MUST
requirement above). However, except when stated otherwise, this
specification does not require the content to be UTF-8, and therefore
(subject to that same requirement) it MAY include octets above and
below 128 mixed arbitrarily.

--
Michael Press