From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Cc: Uwe Brauer <oub@mat.ucm.es>,
emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Non-encoded character in the subject (was: Emacs 21/22: french ç and œ)
Date: Mon, 27 Oct 2008 22:44:14 +0100 [thread overview]
Message-ID: <87bpx5r9w1.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87wsfu5iwr.fsf@mat.ucm.es> (Uwe Brauer's message of "Mon, 27 Oct 2008 13:20:20 +0100")
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):
ELISP> (let ((mm-coding-system-priorities '(iso-8859-1 iso-2022-jp-2 utf-8)))
(rfc2047-encode-string "french ç and œ oe"))
"french =?iso-8859-1?Q?=E7?= and =?iso-2022-jp-2?B?GyQoRClNGyhC?= oe"
ELISP> (let ((mm-coding-system-priorities '(iso-2022-jp-2 utf-8)))
(rfc2047-encode-string "french ç and œ oe"))
"french =?iso-2022-jp-2?B?GyQoRCsuGyhC?= and =?iso-2022-jp-2?B?GyQoRClNGyhC?=\n oe"
ELISP> (let ((mm-coding-system-priorities nil))
(rfc2047-encode-string "french ç and œ oe"))
"french =?utf-8?Q?=C3=A7?= and =?utf-8?Q?=C5=93?= oe"
> My mistake, I presume,
No, your message was encoded correctly, AFAICS:
| Subject: Emacs 21/22: french =?iso-8859-1?q?=E7?= and =?iso-8859-15?q?=BD?=
> but I will ask in the gnus list, I send this mail using xemacs 21.4
> and maybe the Mule support is flawed in gnus. (Or better said in
> xemacs 21.4)
>
> I should have used GNU 21/22 or Xemacs 21.5.
>
> Alas so many emacs(en) around.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2008-10-27 21:44 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 ` Reiner Steib [this message]
2008-10-27 23:57 ` Non-encoded character in the subject Katsumi Yamaoka
2008-10-28 22:03 ` 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=87bpx5r9w1.fsf_-_@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).