From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: message-idna problem
Date: Fri, 26 Sep 2008 08:11:00 +0900 [thread overview]
Message-ID: <b4mbpyb7rej.fsf@jpl.org> (raw)
In-Reply-To: <87skronpc8.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> On Thu, Sep 25 2008, Katsumi Yamaoka wrote:
>> When I send a mail containing the From header like
>>
>> From: 山岡 克美 <yamaoka@jpl.org>
>>
>> the *Messages* buffer collects the following warnings:
>>
>> Unknown symbol: 山
>> Unknown symbol: 岡
>> Unknown symbol: 克
>> Unknown symbol: 美
>>
>> I've never noticed this since I rarely use Japanese names in the
>> message header. It arises if `message-use-idna' is non-nil and
>> there is a name of which the first letter is a non-ASCII character
>> in the header.
> I get "Unknown symbol: Ä" independent on the value of
> `message-use-idna':
ELISP> (let ((message-use-idna nil))
> (mail-header-parse-addresses "Äpfel Birne <foo@bar.invalid>"))
> (("foo@bar.invalid" . "pfel Birne"))
ELISP> (let ((message-use-idna t))
> (mail-header-parse-addresses "Äpfel Birne <foo@bar.invalid>"))
> (("foo@bar.invalid" . "pfel Birne"))
>> Those warnings are the ones that `ietf-drums-parse-addresses'
>> (a.k.a. `mail-header-parse-addresses') that
>> `message-idna-to-ascii-rhs-1' uses issues. Assuming there will
>> potentially be non-ASCII names when `message-idna-to-ascii-rhs-1'
>> runs, how about using `mail-extract-address-components' rather
>> than an ietf-drums- function that does not support non-ASCII
>> characters? This problem might not cause a real harm, though.
> Fine with me.
Thanks. I've modified `message-idna-to-ascii-rhs-1' so as to
use `mail-extract-address-components' rather than
`mail-header-parse-addresses'.
Regards,
prev parent reply other threads:[~2008-09-25 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 10:54 Katsumi Yamaoka
2008-09-25 16:48 ` Reiner Steib
2008-09-25 23:11 ` Katsumi Yamaoka [this message]
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=b4mbpyb7rej.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).