<<< Date Index >>>     <<< Thread Index >>>

Re: [Mutt] #2956: Recipient address broken if containing Š character (UTF-8 code: 0xc5 0xA0)



#2956: Recipient address broken if containing Š character (UTF-8 code: 0xc5 
0xA0)

Comment (by pdmef):

 Replying to [comment:21 Vincent Lefevre]:

 > On 2007-09-18 07:13:35 -0000, Mutt wrote:
 > >  Mutt tries to convert your terminal input in $charset into each of
 > >  charsets speciefied in $send_charset. If it fails with the first one,
 it
 > >  tries the second etc, but if all of them fail, mutt uses your
 terminal's
 > >  $charset.
 > This last feature is a bug: this isn't documented and this isn't what
 > the user wants in general (if the user wants to use the terminal's
 > $charset, he can include it explicitly in $send_charset). There are
 > better solutions such as using a replacement character or returning
 > an error so that the user can fix the header.

 I'd say lacking documentation is the bug (which I've fixed for now). For
 me it makes sense to use $charset as fallback because the text already
 is/was encoded in it, hence mutt can assume it can be converted exactly
 into it.

 However, mutt has to make sure that text fed into it can be properly
 represented in your $charset where IHMO replacement chars and other
 strategies may come into play. It doesn't sound right to me to keep
 invalid data in a session and use some techniques to "validate" it only
 for outgoing data, it should be "valid" in your local session, too so that
 there's no need to "validate" it for outgoing data.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2956#comment:24>