From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: [FIXED] can't forward marked articles
Date: Wed, 17 Dec 2003 15:57:41 +0900 [thread overview]
Message-ID: <b9yd6aoj5i2.fsf@jpl.org> (raw)
Hi again,
I got a bug report that marked articles cannot be forwarded if they
were written by the same author and the author used non-ascii text
in the From header. Here is a backtrace:
Debugger entered--Lisp error: (error "Unknown symbol: \xddb3")
signal(error ("Unknown symbol: \xddb3"))
error("Unknown symbol: %c" 56755)
mail-header-parse-address("\xddb3\xd92c \xdcee\xe47e <yamaoka@jpl.org>")
message-forward-subject-name-subject("Digested Articles")
message-make-forward-subject()
message-forward(nil t)
gnus-uu-digest-mail-forward(nil nil)
gnus-summary-mail-forward(nil)
call-interactively(gnus-summary-mail-forward)
Non-ascii text there is my real name. :)
There are two problems. One is that gnus-summary-mail-forward takes
marked /decoded/ articles by way of gnus-uu-digest-mail-forward, while
gnus-summary-mail-forward itself takes a /raw/ article when forwarding
the current article. The other is that mail-parse functions don't
allow non-ascii text.
I coped with the problem provisionally by using
gnus-extract-address-components instead of mail-header-parse-address.
Although I hesitated to use a Gnus' function in message.el. Or, we
may need to improve gnus-uu.
The reason why I used gnus-extract-address-components rather than
mail-extract-address-components is because it omits a name too much as
follows:
(mail-extract-address-components "Foo (Bar) Baz <foo@bar.baz>")
=> ("Foo Baz" "foo@bar.baz")
(gnus-extract-address-components "Foo (Bar) Baz <foo@bar.baz>")
=> ("Foo (Bar) Baz" "foo@bar.baz")
Regards,
--
Katsumi Yamaoka <yamaoka@jpl.org>
next reply other threads:[~2003-12-17 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 6:57 Katsumi Yamaoka [this message]
2003-12-31 2:10 ` Lars Magne Ingebrigtsen
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=b9yd6aoj5i2.fsf@jpl.org \
--to=yamaoka@jpl.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).