Re: mail-extract-address-components bug

[Katsumi Yamaoka]

>>>>> In <address@hidden> Kenichi Handa wrote:

> Sorry for the late response on this matter.

Please don't mind, since the most important thing now is to release
Emacs 22.1.

> In article <address@hidden>, Katsumi Yamaoka <address@hidden> writes:

>>> I hope this is fixed in Emacs 22.2 (or possibly 22.1).  I've been
>>> annoyed that `mail-extract-address-component' sometimes fails to
>>> parse addresses containing non-ASCII names correctly.  Japanese
>>> people often use their native names in the From header.  Since
>>> they sometimes use non-ASCII letters which are not specified as
>>> words in the syntax table, Gnus, for example, fails to build the
>>> recipient address when replying.

>> [...]

>>> The causes are

>> [...]

>>> and `m-e-a-c' uses `forward-word' to try to skip them even if
>>> they are not words.

>> I found another solution, which doesn't need to modify mail-extr.el:

>> ;; Set the syntax of all non-ASCII characters to `word'
>> ;; in the syntax tables that mail-extr.el uses.

> If it solves the problem, should mail-extr.el be modified to
> setup syntax tables as you did below?

>> (eval-after-load "mail-extr"

I don't want it to be merged in mail-extr.el.  It influences all
the mail-extr processes but I'm not sure whether setting the syntax
of all non-ASCII characters to `word' does not have a side effect.
I consider it is no more than a workaround to be used before
`m-e-a-c' is fixed, and the patch[1] I posted first is better.
But please don't merge it hastily if you have a doubt even if it
is little.

[1] It has to be fixed slightly.  See <address@hidden>.

>> BTW, I think it should be documented that `modify-syntax-entry'
>> allows the generic character of a charset as the first argument,
>> as it is mentioned in the doc string of `make-char'.

> I'm not sure.  It surely accepts a generic character now,
> but the concept of generic character is deleted in
> emacs-unicode-2 branch (and in comming Emacs 23).  So even
> if we describe that feature now, it should be reverted quite
> soon.

I see.  I withdraw the request.

Thanks.