Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Double encoding in ~/Mail/active
Date: Mon, 02 Aug 2010 09:14:08 +0900	[thread overview]
Message-ID: <b4mwrs9kh0v.fsf@jpl.org> (raw)
In-Reply-To: <87tynemvr3.fsf@topper.koldfront.dk>

Adam Sjøgren wrote:
> On Sun, 01 Aug 2010 19:58:26 +0900, Katsumi wrote:
>> Sorry for enbugging.  I'm going to fix it asap.
> Great!
>> Maybe I have to make it encode nnml group names conditionally.

Fixed.  I must apologize to XEmacs users who keep track of the
latest Gnus.  If you have the nnml groups of which the names
contain non-ASCII characters, you want to fix the ~/Mail/active
file, and possibly the ~/.newsrc.eld file, manually.  Beat me!

The purpose of the change I did last was to make sure the names
of groups, that nnmail-split creates[1], in nnml-group-alist are
encoded.  However, it encoded not only newly created group names
but also existing ones.  It happens only in XEmacs.  In Emacs,
the double encoding is not happen even if using encode-coding-string
twice.

(decode-coding-string
 (encode-coding-string
  (encode-coding-string "hyskenstræde" 'utf-8)
  'utf-8)
 'utf-8)
 => "hyskenstræde"

This is why I didn't notice the ill effect of the last change.

[1] The case where the regexps in the splitting rules have
 something like "\\1" that is replaced with the actual text.



  reply	other threads:[~2010-08-02  0:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31 14:03 Stack overflow: Stack overflow in regexp matcher Adam Sjøgren
2010-07-31 22:02 ` Adam Sjøgren
2010-08-01  5:25 ` Adam Sjøgren
2010-08-01  7:55   ` Double encoding in ~/Mail/active Adam Sjøgren
2010-08-01 10:58     ` Katsumi Yamaoka
2010-08-01 11:13       ` Adam Sjøgren
2010-08-02  0:14         ` Katsumi Yamaoka [this message]
2010-08-02 21:43           ` Adam Sjøgren
2010-08-02 23:21             ` Katsumi Yamaoka
2010-08-03  5:54               ` Adam Sjøgren
2010-08-04  0:38                 ` Katsumi Yamaoka

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=b4mwrs9kh0v.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.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).