Comment 48 for bug 369150

(In reply to comment #47)

> Advocacy aside, how do you propose to deal with UTF-8 characters which are not
> re-encodable in Windows-1252 (which is, after all, a "glorified" ISO-8859-1) in
> the example you posted above (comment #43)?

Just as we do now. Replace them with question marks after giving a very conspicuous warning to users that there are characters that cannot be represented in the selected character encoding (they can choose : 'go ahead nonetheless', 'go back to the composition window and change the encoding to UTF-8').

> PS: If you are aware of MUAs that can't deal with properly encoded
> headers/body, please submit them a bug report

I did for a few of them I do occasionally use, but as for others, it's users of those MUAs that need to do that.