#2956: Recipient address broken if containing Š character (UTF-8 code: 0xc5
0xA0)
Comment (by Kyle Wheeler):
{{{
On Sunday, September 16 at 01:30 PM, quoth Vincent Lefevre:
>On 2007-09-14 10:29:34 -0500, Kyle Wheeler wrote:
>> On Friday, September 14 at 03:10 PM, quoth Mutt:
>>> And Mutt has problems if the subject contains such a character too.
>>> See the generated Subject header:
>>>
>>> Subject: Re: [Mutt] #2956: =?UTF-8//TRANSLIT?Q?Reci?=
>>> =?UTF-8//TRANSLIT?Q?pient_address_broken_if_containing_?=
>>> =?UTF-8//TRANSLIT?Q?=C5?= character (UTF-8 code: 0xc5 0xA0)
>>
>> That's broken in more ways than just the space. It should NEVER send
>> strings encoded as "UTF-8//TRANSLIT". I think your $send_charset
setting
>> might be invalid (it should not contain //TRANSLIT).
>
>I do not set $send_charset. My $charset contains //TRANSLIT, but this
>one is correct.
It just occurred to me... given that your $charset is UTF-8, what's
the purpose of //TRANSLIT? All possible characters are displayable in
UTF-8, so //TRANSLIT shouldn't actually be providing any benefit (that
I'm aware of). Is there something I'm missing?
~Kyle
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/2956#comment:>
