From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: posting-charset abolition
Date: Fri, 01 Nov 2002 11:43:52 +0900 [thread overview]
Message-ID: <yotlvg3i6mc7.fsf@jpl.org> (raw)
In-Reply-To: <4n3cqmy93k.fsf@benko.bwh.harvard.edu>
>>>>> In <4n3cqmy93k.fsf@benko.bwh.harvard.edu>
>>>>> Ted Zlatanov <tzz@lifelogs.com> wrote:
> I think the simplest programmatic solution is to scan the message
> buffer right before sending, when it's already encoded, and add the
> CTE: 8bit header if any 8-bit characters are detected.
Yes. It can be done by using message-header-hook or something.
However, though I haven't seen the source code in details yet, I
think there is a more smart solution. Because, even if I use
the following codes to remove CTE:8, CTE is added if necessary.
(eval-after-load "gnus-msg"
'(if (boundp 'gnus-group-posting-charset-alist)
(let ((news (assq 'message-this-is-news
gnus-group-posting-charset-alist)))
(if news
(setcdr news '(nil nil))))))
> But I still
> think this is unnecessary work for other than aesthetic reasons, as
> very few MTAs today do 7bit CTE, and setting the header to 8bit is
> harmless to 7bit data.
To be sure, it is right. However, would you allow me if it is
achieved with a trifling change?
> I don't understand the statement about "vicious MUAs rampant."
Possibly my talk was too acrimoniously. Never mind please.
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2002-11-01 2:43 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
2002-10-31 12:38 ` Katsumi Yamaoka
2002-10-31 14:30 ` Ted Zlatanov
2002-11-01 2:43 ` Katsumi Yamaoka [this message]
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=yotlvg3i6mc7.fsf@jpl.org \
--to=yamaoka@jpl.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).