Re: naive charset question

[Ken Raeburn <raeburn@raeburn.org>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai writes:
> I don't usually try to create such messages, but not so long ago the
> splitting still worked.  Hm.  Let me try it with this message:

That come through fine for me, although if I try to quote the
non-ASCII characters in a reply, again I get asked for a charset and
the default behavior is to send a one-part us-ascii message.  Does
quoting in a reply work for you, or sending the HELLO text, as opposed
to actually entering the characters as input?

It's also interesting that your last name and the closing paren was
dropped from the attribution above, and my buffer name displays as
"*wide reply to Kai Gro\337johann*".  In the summary buffer that
character displays as an open block, and only the article buffer
actually gets it right.  I also get the \337 if I use M-w and C-y to
copy your name into a new buffer.