[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#19431: 24.4; Bad handling of RFC2047 encoded headers by 'mail-extrac
From: |
Lars Ingebrigtsen |
Subject: |
bug#19431: 24.4; Bad handling of RFC2047 encoded headers by 'mail-extract-address-components' |
Date: |
Sun, 15 Apr 2018 19:51:13 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Enrico Scholz <enrico.scholz@sigma-chemnitz.de> writes:
> the emacs email framework fails on email addresses containing umlauts.
> E.g. in the following example
>
> --- {{{ snip ---
> ; set a (nearly) real-world To: address; the umlaut '=C3=A4' encoding
> ; was replaced by '=61=65'
> (let* ((address "=?utf-8?Q?B=61=65Br=2C_Klaus?= <test@example.com>")
> (decoded (rfc2047-decode-string address)))
> ; show output with encoded umlauts and non-RFC2047 header
> (print (mail-extract-address-components "\"Baer, Klaus\"
> <test@example.com>"))
> (print address t)
> (print decoded t)
> ; previous prints were just for debugging purposes; now, the real
> ; functions will be called...
> (print (mail-extract-address-components address))
> (print (mail-extract-address-components decoded)))
Yes, that's a very confusing and not very useful function. I've now
updated the doc string to point to `mail-header-parse-address', which is
the function that should be used to parse address headers, and does the
right thing also on German addresses.
I don't think it's worth trying to fix the mess that is
`mail-extract-address-components'.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#19431: 24.4; Bad handling of RFC2047 encoded headers by 'mail-extract-address-components',
Lars Ingebrigtsen <=