From: stormwatch <ezebirman@gmail.com>
To: info-gnus-english@gnu.org
Subject: nnmail split multi-byte bug or feature?
Date: Tue, 27 Jul 2010 04:56:39 -0700 (PDT) [thread overview]
Message-ID: <eca53321-ad43-41c8-ae61-c5fffeb7795c@p11g2000prf.googlegroups.com> (raw)
Note: It seems that the original message sent thorugh
news.individual.net was not delivered.
I did set this nnmail split method
("mail.utn.campusvirtual.\\1" "^X-Course-Name: \\(.*\\)$")
The problem is that the matched text is multi-byte encoded. Setting
(setq nnmail-mail-splitting-decodes t) did the trick. Well, almost,
because the group name shown in the *Group* buffer is:
28: mail.utn.campusvirtual.ingenier\355a y sociedad
instead of:
28: mail.utn.campusvirtual.ingeniería y sociedad
The dir '/home/stormwatch/Mail/mail/utn/campusvirtual/ingeniería y
sociedad' was created by gnus but I could not view the summary of the
group; not until I created a symlink with a latin-1 encoded dirname by
means of convmv:
david :: mail/utn/campusvirtual » ls -l
total 4
lrwxrwxrwx 1 stormwatch stormwatch 22 jul 22 05:09 ingenier?a y
sociedad -> ingeniería y sociedad
drwxrwxr-x 2 stormwatch stormwatch 4096 jul 22 05:19 ingeniería y
sociedad
My locale is utf-8 (LANG=es_AR.UTF-8)
--
Ezequiel Birman
next reply other threads:[~2010-07-27 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 11:56 stormwatch [this message]
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
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=eca53321-ad43-41c8-ae61-c5fffeb7795c@p11g2000prf.googlegroups.com \
--to=ezebirman@gmail.com \
--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).