On 2007-09-17 17:09:55 +0200, Rocco Rutte wrote: > * Kyle Wheeler [07-09-17 09:39:02 -0500] wrote: >> If mutt is generating this, then something is wrong... perhaps mutt >> should recognize and strip out //TRANSLIT strings? > > Yes, but that's another issue (it already has a table of valid character > set names, it just needs to match them for $send_charset).
Mutt doesn't need to recognize //TRANSLIT strings. The fact that I have a //TRANSLIT string in my $charset should not have any effect on what Mutt sends. $charset is only a terminal-related variable: Character set your terminal uses to display and enter textual data. [...] > So technically it invalidates the UTF-8 itself and afterwards more > or less encodes the broken subject, I think. Yes, but this doesn't explain why Mutt generates something with //TRANSLIT in the headers. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
