From: Simon Josefsson <simon@josefsson.org>
To: Frank Schmitt <ich@frank-schmitt.net>
Cc: 1174@emacsbugs.donarmstrong.com, ding@gnus.org
Subject: bug#1174: 23.0.60; Some UTF-8 mails displaying wrongly in Emacs 23
Date: Mon, 12 Jan 2009 11:54:01 +0100 [thread overview]
Message-ID: <87hc44hk1i.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <878wr2ohde.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Sat, 29 Nov 2008 13:18:21 +0100")
I have recently upgraded my Gnus installation, and it included this fix.
Now every e-mail I send has non-ASCII characters pre-fixed with \201.
So the patch installed does not seem to be the right, or there is
something else wrong with my configuration. Can anyone else reproduce
this? I'm including 'åäö' in this e-mail for debugging.
I'll see if I can debug this further, and find the exact part of the
patch that cause the problem.
/Simon
Simon Josefsson <simon@josefsson.org> writes:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>> On Fri, Oct 17 2008, Frank Schmitt wrote:
>>
>>> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>>
>>>> On Fri, Oct 17 2008, Stefan Monnier wrote:
>>>>
>>>>>> ;; 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) so feel free to
> revert the patch or apply another patch instead. It needs to be tested
> under Emacs 22 too, though, if it is installed in the Gnus CVS.
>
> /Simon
next prev parent reply other threads:[~2009-01-12 10:54 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
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 ` Simon Josefsson [this message]
2009-01-12 11:03 ` bug#1174: 23.0.60; Some UTF-8 mails displaying wrongly in Emacs 23 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=87hc44hk1i.fsf@mocca.josefsson.org \
--to=simon@josefsson.org \
--cc=1174@emacsbugs.donarmstrong.com \
--cc=ding@gnus.org \
--cc=ich@frank-schmitt.net \
/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).