From: Pavel.Janik@inet.cz (Pavel Janik ml.)
Subject: Re: Content-Transfer-Encoding
Date: 22 Apr 2000 10:43:27 +0200 [thread overview]
Message-ID: <m3og727cgg.fsf@SnowWhite.inet.cz> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "22 Apr 2000 02:16:28 +0200"
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Date: 22 Apr 2000 02:16:28 +0200
Hi,
> > hmm, can you please add (iso-8859-2 . 8bit)?
>
> Is that the preferred encoding, though? Why not qp?
there are at least two good reasons:
- there are too many people with not-MIME compliant browsers and they
can not read =3D like stuff at all. 8bit is readable for
them. Remember that there are crazy people who do not use Gnus and
even Emacs...
- if you send something with qp, the first well configured server does
recode the stuff to 8bit :-) so it is better to directly send with
8bit and you will have easily grep'able mail archive. I do not think
that Gnus or anything in Emacs is good for grepping through my 100MB+
mail archive...
The last reason can be that =3D is three bytes long, but = is only one byte. I
think you can find more resons for this...
--
Pavel Janík ml.
Pavel.Janik@inet.cz
next prev parent reply other threads:[~2000-04-22 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-13 10:23 Content-Transfer-Encoding Shigeki Uno
2000-01-13 11:14 ` Content-Transfer-Encoding Katsumi Yamaoka
2000-01-13 17:02 ` Content-Transfer-Encoding Shigeki Uno
2000-01-13 23:52 ` Content-Transfer-Encoding Katsumi Yamaoka
2000-01-14 18:18 ` Content-Transfer-Encoding Shigeki Uno
2000-04-21 13:22 ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2000-04-21 19:24 ` Content-Transfer-Encoding Pavel Janik ml.
2000-04-22 0:16 ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2000-04-22 8:43 ` Pavel Janik ml. [this message]
2000-04-22 12:28 ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2001-01-09 10:37 content-transfer-encoding vvv
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=m3og727cgg.fsf@SnowWhite.inet.cz \
--to=pavel.janik@inet.cz \
/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).