From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: ding@gnus.org
Subject: Re: quoted-printable no-go in news?
Date: 07 Apr 2003 15:29:11 -0700 [thread overview]
Message-ID: <863ckuj614.fsf@red.stonehenge.com> (raw)
In-Reply-To: <m37ka6nlf4.fsf@merlin.emma.line.org>
>>>>> "Matthias" == Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
Matthias> Gnus displays wide hollow boxes instead of the umlauts in
Matthias> Message-ID: <etvq8vonajs2p1llpmfpnl8d0rehmsdu5u@4ax.com>
Matthias> (de.rec.fotografie) -- it is declared iso-8859-1 and
Matthias> quoted-printable; but Gnus nicely and correctly displays
Matthias> "\200" for a b0rken =80. Later, when following up to the
Matthias> post, Gnus complains about unprintable characters and offers
Matthias> to replace, remove, ignore, ... them. It works in
Matthias> binary-encoded articles.
The only acceptable "encoding" for Usenet at large in the text
newsgroups that I'm aware of is plain 7-bit ASCII, although I imagine
iso-8859-1 is probably also acceptable. Quoted-printable, definitely
not.
However, maybe de.* has a different rule.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2003-04-07 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 19:43 Matthias Andree
2003-04-07 22:29 ` Randal L. Schwartz [this message]
2003-04-08 5:59 ` Graham Murray
2003-04-10 17:44 ` Matthias Andree
2003-04-08 11:48 ` Jesper Harder
2003-04-10 19:06 ` Matthias Andree
2003-04-10 19:39 ` Matthias Andree
2003-04-10 23:25 ` Reiner Steib
2003-04-10 20:26 ` Jesper Harder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=863ckuj614.fsf@red.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).