Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: info-gnus-english@gnu.org
Subject: Re: nnmail split multi-byte bug or feature?
Date: Thu, 29 Jul 2010 10:09:28 +0900	[thread overview]
Message-ID: <b4mlj8v856f.fsf@jpl.org> (raw)
In-Reply-To: <3b440960-4153-4dff-8971-db813ea29aa3@f6g2000yqa.googlegroups.com>

Newsgroups: gnu.emacs.gnus
Cc: info-gnus-english@gnu.org

stormwatch wrote:
> On Jul 27, 9:04 pm, Katsumi Yamaoka <yama...@jpl.org> wrote:
[...]
>> What is the mail back end you use?  As for the most recent Gnus:
[...]
> I use nnml and gnus included in an up-to-date emacs built from bzr.

Hmm, for the most recent Gnus there should be nothing you have
to do as you are in the utf-8 locale.

> Variables that might have to do with this problem:

> gnus-group-name-charset-method-alist is a variable defined in `gnus-
> group.el'.
> Its value is nil

ok.

> gnus-group-name-charset-group-alist is a variable defined in `gnus-
> group.el'.
> Its value is ((".*" . utf-8))

ok.

> nnmail-pathname-coding-system is a variable defined in `nnmail.el'.
> Its value is nil

It should be ok, but I had set it to utf-8.  I don't recall why
I did it.  But I verified now that nil is ok for non-ASCII group
names.

> file-name-coding-system is a variable defined in `C source code'.
> Its value is nil

ok.

> default-file-name-coding-system is a variable defined in `C source
> code'.
> Its value is utf-8-unix

ok.

> and also, this info node seems relevant:
> 2.17 Accessing groups of non-English names
> ==========================================
> ...
>    Note that when you copy or move articles from a non-ASCII group to
> another group, the charset used to encode and decode group names
> should
> be the same in both groups.  Otherwise the Newsgroups header will be
> displayed incorrectly in the article buffer.

[...]

> Perhaps the problem arised because I respooled the messages. ¿Would
> you be so kind as to try the same and see if you can reproduce the bug/
> feature?

No problem here.  What I did was:

1. Move articles in
   nnml:mail.utn.campusvirtual.ingeniería y sociedad
   to nnml:tmp .
2. `C-u G DEL' to delete
   nnml:mail.utn.campusvirtual.ingeniería y sociedad .
3. `B r' in nnml:tmp to respool the mails that have the header:
   X-Course-Name: ingeniería y sociedad
4. Confirm "nnml:mail.utn.campusvirtual.ingeniería y sociedad" is
   created and mails are spooled there.

> I, otoh, will try to remove everything and create a shiny
> brand-new fake-with-the-fingers-crossed incoming message.

BTW, I noticed `B nnml RET RET' in the group buffer shows
non-ASCII group names without properly decoding.  It should be
fixed!  How do you find possibly unknown mail groups that
nnmail-split creates?  (Text that X-Course-Name header contains
is unknown, isn't it?)

  parent reply	other threads:[~2010-07-29  1:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 11:56 stormwatch
2010-07-28  0:04 ` Katsumi Yamaoka
     [not found] ` <mailman.20.1280275492.14690.info-gnus-english@gnu.org>
     [not found]   ` <3b440960-4153-4dff-8971-db813ea29aa3@f6g2000yqa.googlegroups.com>
2010-07-29  1:09     ` Katsumi Yamaoka [this message]
2010-07-30  2:09       ` Katsumi Yamaoka
     [not found]       ` <mailman.6.1280455794.998.info-gnus-english@gnu.org>
2010-08-01  0:06         ` stormwatch
2010-08-02  0:36           ` Katsumi Yamaoka
2010-08-02  6:00             ` 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=b4mlj8v856f.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=info-gnus-english@gnu.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).