From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: Uwe Brauer <oub@mat.ucm.es>,
emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Non-encoded character in the subject
Date: Tue, 28 Oct 2008 08:57:08 +0900 [thread overview]
Message-ID: <b4mej211tij.fsf@jpl.org> (raw)
In-Reply-To: <87bpx5r9w1.fsf_-_@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> On Mon, Oct 27 2008, Uwe Brauer wrote:
>>>>>>> "Miles" == Miles Bader <miles@gnu.org> writes:
>>
>>> Hmm, why did gnus (message-mode) only encode the first non-ascii
>>> character in the Subject: header? Odd... Lemme try again...
> The `œ' isn't encode, but sent as a raw iso-2022-7bit character
> (character U+001B replaced with <ESC>):
>| Subject: Re: Emacs 21/22: french =?iso-8859-1?q?=E7?= and <ESC>$(D)M<ESC>(B
> I cannot reproduce this, neither with Emacs 22.1 nor with current
> Emacs trunk (2008-10-25):
If the subject is encoded correctly when performing
C-u C-c C-m P
in the message buffer, the culprit is not Gnus in all likelihood.
It might be MTA's doing. Though it doesn't come under the case,
Reiner's message I received from the MS Exchange POP server is
broken as follows:
Subject:
=?Windows-1252?Q?Non-encoded_character_in_the_subject_(was:_Emacs_21/22:_?=
=?Windows-1252?Q?_french_=E7_and_=C5=93)?=
i.e.,
Subject:
Non-encoded character in the subject (was: Emacs 21/22: french ç and Å“)
But no problem in the same message having reached Gmane.
Regards,
next prev parent reply other threads:[~2008-10-27 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ljwa6zjj.fsf@mat.ucm.es>
[not found] ` <buobpx66yc8.fsf@dhapc248.dev.necel.com>
[not found] ` <buo63ne6y7q.fsf_-_@dhapc248.dev.necel.com>
[not found] ` <87wsfu5iwr.fsf@mat.ucm.es>
2008-10-27 21:44 ` Non-encoded character in the subject (was: Emacs 21/22: french ç and œ) Reiner Steib
2008-10-27 23:57 ` Katsumi Yamaoka [this message]
2008-10-28 22:03 ` Non-encoded character in the subject Reiner Steib
2008-10-28 23:49 ` Katsumi Yamaoka
2008-10-29 1:04 ` Miles Bader
2008-10-31 4:51 ` Miles Bader
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=b4mej211tij.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=oub@mat.ucm.es \
/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).