Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: ding@gnus.org
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-devel@gnu.org
Subject: Re: Non-encoded character in the subject
Date: Fri, 31 Oct 2008 13:51:05 +0900	[thread overview]
Message-ID: <buoabclgyfa.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <87r660pecj.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Tue, 28 Oct 2008 23:03:08 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:
> Uh, this is the first time I hear that MTAs are changing the MIME
> encoding of mail headers (I know about MTAs converting the
> Content-Transfer-Encoding, e.g. qp <-> 8bit, of the body).

My "original" (written by FCC: into a local file here) message has this:

   Subject: Re: Emacs 21/22:  french =?iso-8859-1?Q?=E7?= and
    =?iso-2022-jp-2?B?GyQoRClNGyhC?=

but the copy of that same message I get via NNTP from Gmane has this:

   Subject: Re: Emacs 21/22:  french =?iso-8859-1?q?=E7?= and ^[$(D)M^[(B

where I've replaced literal ESC characters with the two-character
sequence ^[ in this reply.

-Miles

-- 
Road, n. A strip of land along which one may pass from where it is too
tiresome to be to where it is futile to go.




      parent reply	other threads:[~2008-10-31  4:51 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         ` 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 [this message]

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=buoabclgyfa.fsf@dhapc248.dev.necel.com \
    --to=miles@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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).