From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Another problem with rfc2047 encoding
Date: Mon, 28 Apr 2003 19:20:16 +0200 [thread overview]
Message-ID: <v91xzmh73j.fsf@marauder.physik.uni-ulm.de> (raw)
Hi,
when posting a subject like...
| ¿Qué significa =?ISO-8859-1?Q?=F6?= en el Asunto?
... or...
| Ich hab' da mal 'ne Fräge: Was bedeuten denn diese Zeichen =?ISO-8859-1?Q?=F6?= ?
... Oort Gnus (CVS) doesn't treat "=?ISO-8859-1?Q?=F6?=" literal as it
should. "=?" or/and "?=" would have to be encoded, probably.
,----[ (1) <v9k7deg3aj.fsf@marauder.physik.uni-ulm.de> / Oort ]
| Subject: =?iso-8859-1?q?=BFQu=E9?= significa =?ISO-8859-1?Q?=F6?= en el
| Asunto?
`----
I.e. this will be decoded to "¿Qué significa ö en el Asunto?", which
is wrong.
Gnus 5.9 (from Emacs 21.3) does it correctly:
,----[ (2) <v9k7dea87n.fsf@theotp2.physik.uni-ulm.de> / Gnus 5.9 ]
| Subject: =?iso-8859-1?q?=BFQu=E9_significa_=3D=3FISO-8859-1=3FQ=3F=3DF6?=
| =?iso-8859-1?q?=3F=3D_en_el_Asunto=3F__(Gnus_5.9)?=
`----
I didn't follow the discussion about "rfc2047 still bogus" on
bugs@gnus.org closely, but this might be related:
,----[ `rfc2047.el' from Oort ]
| ELISP> (load ".../share/emacs/site-lisp/gnus-Oort/rfc2047.elc")
| t
| ELISP> (with-temp-buffer
| (insert "Subject: ¿Qué significa =?ISO-8859-1?Q?=F6?= en el Asunto?\n")
| (rfc2047-encode-message-header)
| (buffer-string))
| "Subject: =?iso-8859-1?q?=BFQu=E9?= significa =?ISO-8859-1?Q?=F6?= en el\n Asunto?\n"
`----
,----[ `rfc2047.el' from Emacs 21.3 ]
| ELISP> (load ".../share/emacs/21.3/lisp/gnus/rfc2047.elc")
| t
| ELISP> (with-temp-buffer
| (insert "Subject: ¿Qué significa =?ISO-8859-1?Q?=F6?= en el Asunto?\n")
| (rfc2047-encode-message-header)
| (buffer-string))
| "Subject: =?iso-8859-1?q?=BFQu=E9_significa_=3D=3FISO-8859-1=3FQ=3F=3DF?=\n =?iso-8859-1?q?6=3F=3D_en_el_Asunto=3F?=\n"
`----
Bye, Reiner.
(1) nntp://news.gmane.org/gmane.test/620
(2) nntp://news.gmane.org/gmane.test/624
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next reply other threads:[~2003-04-28 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 17:20 Reiner Steib [this message]
2003-04-28 20:47 ` Reiner Steib
2003-05-01 6:38 ` Lars Magne Ingebrigtsen
2003-05-01 6:49 ` Thomas Hühn
2003-05-01 7:14 ` Lars Magne Ingebrigtsen
2003-05-01 7:39 ` Thomas Hühn
2003-05-01 14:48 ` Lars Magne Ingebrigtsen
2003-05-04 19:42 ` Christoph Garbers
2003-05-08 22:49 ` Dave Love
2003-05-15 17:26 ` Christoph Garbers
2003-05-16 16:42 ` Dave Love
2003-05-20 12:42 ` Christoph Garbers
2003-05-22 17:01 ` Dave Love
2003-05-01 8:15 ` Bjørn Mork
2003-05-01 8:42 ` Lars Magne Ingebrigtsen
2003-05-01 12:46 ` Simon Josefsson
2003-05-01 13:28 ` Bjørn Mork
2003-05-02 16:10 ` Lars Magne Ingebrigtsen
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=v91xzmh73j.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).