From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Simon Josefsson <simon@josefsson.org>
Cc: Frank Schmitt <ich@frank-schmitt.net>,
James Cloos <cloos@jhcloos.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
ding@gnus.org, 1174@emacsbugs.donarmstrong.com,
Clemens Schueller <cs.usenet.nospam@aon.at>
Subject: Re: bug#1174: 23.0.60; Some UTF-8 mails displaying wrongly in Emacs 23
Date: Sat, 29 Nov 2008 16:30:18 +0100 [thread overview]
Message-ID: <87d4geim7p.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <878wr2ohde.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Sat, 29 Nov 2008 13:18:21 +0100")
On Sat, Nov 29 2008, Simon Josefsson wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>>>>> ;; BEWARE: we used to use string-as-multibyte here which is braindead
>>>>>> ;; because it will turn accidental emacs-mule-valid byte sequences
>>>>>> ;; into multibyte chars. --Stef
>>>>>> ;; Reverted, braindead got 7.5 out of 10 on imdb, so it can't be
>>>>>> ;; that bad. --Simon
>>
>> Simon, could you please clarify why you reverted Stefan's change in
>> `nnimap-demule'? It breaks reading UTF-8 articles via nnimap.el in
>> Emacs 23.
>
> I don't recall, but people should notice relatively quickly if there are
> problems in this area (wrong display of non-ascii)
Hm, both changes happened 2004, but I don't recall any reports beside
the recent ones in 2008:
http://thread.gmane.org/gmane.emacs.gnus.general/67112
(bug#464, reported by James Cloos)
http://thread.gmane.org/gmane.emacs.bugs/21524
(bug#1174, reported by Frank Schmitt)
----------------------------
revision 7.9
date: 2004-09-13 13:52:48 +0200; author: jas; state: Exp; lines: +5 -3
(nnimap-demule): Revert 2004-08-30 change.
----------------------------
> so feel free to revert the patch or apply another patch instead. It
> needs to be tested under Emacs 22 too, though,
I never saw this problem myself. I cannot see any difference with a
few UTF-8 articles (C-T-E: 8bit, [1]), neither with Emacs 22 (with
current Gnus trunk) or Emacs trunk (Gnus 5.13 from there). Stefan,
what are the "accidental emacs-mule-valid byte sequences" that trigger
this problem? It would be good if someone could send me a problematic
article. [2]
I've just checked in (Gnus and Emacs) some code to debug this problem.
I'd like to ask those who saw the bug in Emacs 23 to test the articles
in question:
- With current Emacs 23 (Emacs CVS trunk)
- With Emacs 22 plus current Gnus CVS trunk (No Gnus)
- If you see wrong display: does it display correctly after evaluating
the following:
M-x gnus-backlog-shutdown RET
(setq nnimap-demule-use-string-to-multibyte nil
gnus-verbose 10)
Check the *Messages* buffer for messages
"nnimap-demule-use-string-to-multibyte: nil" to ensure that the
article is decoded again with this setting. You may need to
re-enter the group.
> if it is installed in the Gnus CVS.
I don't want different code in Gnus and Emacs. If all else fails, we
can make it conditional.
Bye, Reiner.
[1] Cc-s of the following articles (available on Gmane) from Aidan Kehoe:
<18492.30425.377545.700503@parhasard.net>
<18518.43672.183610.662699@parhasard.net>
<18712.43474.265690.792714@parhasard.net>
Non-ascii characters in the attribution line ("scríobh"), the
signature ("¿Dónde estará ahora mi sobrino Yoghurtu Nghé ..."),
and "’", "İ", "ı"
[2] (push '(utf-8 . 8bit) mm-body-charset-encoding-alist)
--> trying to produce a problematic article here:
AE-Ä OE-Ö UE-Ü ae-ä oe-ö ue-ü ss-ß
Should be sent with:
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-11-29 15:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m37i89boe6.fsf@mid.gehheimdienst.de>
[not found] ` <jeabd5vvug.fsf@sykes.suse.de>
[not found] ` <m363ntey23.fsf@mid.gehheimdienst.de>
[not found] ` <u63nso2wk.fsf@gnu.org>
[not found] ` <jebpxjvd53.fsf@sykes.suse.de>
[not found] ` <m3ej2fd2o0.fsf@mid.gehheimdienst.de>
[not found] ` <umyh3mttj.fsf@gnu.org>
[not found] ` <m33aivfsa8.fsf@mid.gehheimdienst.de>
[not found] ` <jwv8wsnjknd.fsf-monnier+emacsbugreports@gnu.org>
2008-10-17 18:19 ` Reiner Steib
2008-10-17 18:36 ` Frank Schmitt
2008-11-29 12:08 ` Reiner Steib
2008-11-29 12:18 ` Simon Josefsson
2008-11-29 15:30 ` Reiner Steib [this message]
2008-11-29 21:30 ` Stefan Monnier
2008-11-30 13:12 ` Reiner Steib
2008-11-29 22:14 ` James Cloos
2008-11-30 13:11 ` View articles with different charset (was: bug#1174: 23.0.60; Some UTF-8 mails displaying wrongly in Emacs 23) Reiner Steib
2008-11-30 21:23 ` View articles with different charset James Cloos
2009-01-12 10:54 ` bug#1174: 23.0.60; Some UTF-8 mails displaying wrongly in Emacs 23 Simon Josefsson
2009-01-12 11:03 ` Frank Schmitt
2009-01-12 11:10 ` Simon Josefsson
2009-01-14 11:20 ` Gabor Z. Papp
2009-01-14 20:12 ` Reiner Steib
2009-01-14 22:08 ` Stefan Monnier
2008-12-01 21:04 ` Stefan Monnier
2008-12-01 22:48 ` Reiner Steib
2008-12-02 7:36 ` Stefan Monnier
2008-12-04 19:43 ` Reiner Steib
2008-12-04 21:43 ` Frank Schmitt
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=87d4geim7p.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=1174@emacsbugs.donarmstrong.com \
--cc=Reiner.Steib@gmx.de \
--cc=cloos@jhcloos.com \
--cc=cs.usenet.nospam@aon.at \
--cc=ding@gnus.org \
--cc=ich@frank-schmitt.net \
--cc=monnier@iro.umontreal.ca \
--cc=simon@josefsson.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).