From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-pretest-bug@gnu.org, Zhang Wei <id.brep@gmail.com>,
ding@gnus.org, Kenichi Handa <handa@m17n.org>
Subject: Re: `.newsrc.eld' saves chinese group name in wrong coding
Date: Thu, 19 Oct 2006 12:56:29 +0900 [thread overview]
Message-ID: <b4m4pu1m00i.fsf@jpl.org> (raw)
In-Reply-To: <87mz7tm2wn.fsf@furball.mit.edu>
>>>>> In <87mz7tm2wn.fsf@furball.mit.edu>
>>>>> Chong Yidong <cyd@stupidchicken.com> wrote:
> Zhang Wei <id.brep@gmail.com> writes:
>> `.newsrc.eld' can't save chinese group name in proper coding. When gnus
>> is restarted, all of the articles in groups with chinese name are marked
>> unread. But enter that group, you will find all of the articles are old
>> articles (marked by an `O'). The file in the attachment is the wrong
>> formatted `.newsrc.eld', hope that will be helpful.
> The problem seems to be that when a Chinese group name is given, e.g.
> "好", `gnus-group-insert-group-line' ends up calling
> (decode-coding-string "好" 'utf-8)
> which gives gibberish. Could either the coding systems experts
> (i.e. Handa) or Gnus experts tell us why this is the wrong thing to
> do?
Gnus uses utf-8 encoded non-ASCII group names internally, those
encoded names are saved in the .newsrc.eld file, and they are
decoded by utf-8 when displaying. I had no problem when I once
tried nnrss groups with Japanese names. So, I cannot imagine
what is happening with Zhang Wei, sorry.
> I think the way to reproduce this is as follows:
> 1. save an empty file with a Chinese filename:
> C-x C-f 好 RET RET C-x C-s
> (I simply copied the character into the minibuffer from the HELLO
> file.)
> 2. go to the Gnus group buffer:
> M-x gnus RET
> 3. Open that file as a Gnus group:
> G f
> => Gnus group line is shown in Gibberish
It is caused because of the default value of
`gnus-group-name-charset-group-alist'. It can be fixed with the
following:
(push '("\\`nndoc\\(\\+?[^:]+\\)?:")
gnus-group-name-charset-group-alist)
However, I'm not quite sure making it the new default is
generally good.
Regards,
next prev parent reply other threads:[~2006-10-19 3:56 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ufydnay6j.fsf@gmail.com>
2006-10-19 2:54 ` Chong Yidong
2006-10-19 3:56 ` Katsumi Yamaoka [this message]
2006-10-19 4:11 ` Katsumi Yamaoka
2006-10-19 8:33 ` Reiner Steib
2006-10-19 9:03 ` Katsumi Yamaoka
2006-10-20 3:39 ` Chong Yidong
2006-10-20 4:06 ` Katsumi Yamaoka
2006-10-20 5:18 ` Katsumi Yamaoka
2006-10-20 6:04 ` Eli Zaretskii
2006-10-20 6:21 ` Katsumi Yamaoka
2006-10-20 6:38 ` Eli Zaretskii
2006-10-20 8:59 ` Katsumi Yamaoka
2006-10-21 2:03 ` Richard Stallman
2006-10-22 23:28 ` Katsumi Yamaoka
2006-10-23 11:45 ` Richard Stallman
2006-10-20 19:19 ` Stefan Monnier
2006-10-20 20:30 ` Eli Zaretskii
2006-10-20 22:06 ` Stefan Monnier
2006-10-21 9:22 ` Eli Zaretskii
2006-10-23 3:55 ` Stefan Monnier
2006-10-23 4:16 ` Eli Zaretskii
2006-10-23 19:11 ` Stefan Monnier
2006-10-23 20:06 ` Eli Zaretskii
2006-10-23 20:49 ` Stefan Monnier
2006-10-24 4:17 ` Eli Zaretskii
2006-10-24 15:22 ` Stefan Monnier
2006-10-24 17:27 ` Eli Zaretskii
2006-10-24 18:03 ` Stefan Monnier
2006-10-25 18:02 ` Richard Stallman
2006-10-25 20:22 ` Eli Zaretskii
2006-10-26 8:52 ` Richard Stallman
2006-10-27 8:05 ` Eli Zaretskii
2006-10-27 13:33 ` Richard Stallman
2006-10-27 14:27 ` Stefan Monnier
2006-10-28 18:13 ` Richard Stallman
2006-10-28 10:28 ` Eli Zaretskii
2006-10-29 18:45 ` Richard Stallman
2006-10-23 11:45 ` Richard Stallman
2006-10-23 19:16 ` Stefan Monnier
2006-10-24 17:43 ` Richard Stallman
2006-10-24 18:14 ` Stefan Monnier
2006-10-25 18:03 ` Richard Stallman
2006-10-25 18:03 ` Richard Stallman
2006-10-27 2:48 ` Kenichi Handa
2006-10-21 1:01 ` Kenichi Handa
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=b4m4pu1m00i.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=handa@m17n.org \
--cc=id.brep@gmail.com \
/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).