Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: posting-charset abolition
Date: Thu, 31 Oct 2002 06:34:25 -0500	[thread overview]
Message-ID: <m3of9ahmf2.fsf@heechee.beld.net> (raw)
In-Reply-To: <yotlof9c9ier.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 30 Oct 2002 22:15:56 +0900")

On Wed, 30 Oct 2002, yamaoka@jpl.org wrote:
> Gnus always puts the ``Content-Transfer-Encoding: 8bit'' header
> into news articles to be sent by default.  Since Japanese news
> articles use the iso-2022-jp charset normally, putting CTE: 8bit
> is nonsense (iso-2022-jp never uses 8-bit data).

Forgive my ignorance, but I don't understand why CTE: 8bit needs to be
removed for 7bit encodings.  Does the 7bit CTE save bits or processing
time when the message is delivered (my understanding is that this used
to be the case long ago, but today very few active MTAs use 7bit)?
Does the 8bit CTE somehow distort any of the current 7bit encodings?
If the answer to both questions is no, maybe it's best to leave the
CTE at 8bit.

Ted




  parent reply	other threads:[~2002-10-31 11:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 13:15 Katsumi Yamaoka
2002-10-31  9:12 ` Katsumi Yamaoka
2002-10-31 11:34 ` Ted Zlatanov [this message]
2002-10-31 12:38   ` Katsumi Yamaoka
2002-10-31 14:30     ` Ted Zlatanov
2002-11-01  2:43       ` Katsumi Yamaoka
2002-11-01  3:07         ` Ted Zlatanov
2002-11-01  6:51         ` Jesper Harder
2002-11-01  8:20           ` Katsumi Yamaoka
2002-11-01 12:33             ` Katsumi Yamaoka
2002-11-01 14:18               ` Jesper Harder
2002-11-01 15:54                 ` Katsumi

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=m3of9ahmf2.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    /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).