Re: mail-extract-address-components extract modified full name

[Katsumi Yamaoka]

>>>>> In <address@hidden> Katsumi Yamaoka wrote:

> mail-header-parse-address doesn't support non-ASCII characters,
> so a function like gnus-extract-address-components is also
> needed.

In my opinion, we need a much simpler function to replace the
present mail-extract-address-components.  The required feature
is only to parse the following four patterns:

ADRESS
<ADRESS>
ADRESS (NAME)
NAME <ADDRESS>

They may be combined separated with commas of course.  The NAME
portion may contain non-ASCII characters.  The NAME and ADDRESS
portions should never be modified.  Otherwise, it may be
sufficient to separate functions concerned with customs or
languages from the present mail-extract-address-components.  For
the later case, here's a way to explain what I'd like to say,
for example:

(defvar mail-extr-enable-voodoo nil "*docstring.")

(defun mail-extract-address-components (address &optional all)
  [...]
          (when mail-extr-enable-voodoo
            (mail-extr-voodoo ...))

I noticed mail-extract-address-components is a too complicated
function recently, in spite of the name looks like a standard
Emacs function.  Especially, it often breaks Japanese personal
names.  The attached picture is a collection of how m-e-a-c
works bad: