till wrote:
The other option (and this is *shudder* recommended in the HTML 5 RFC) is to just always decode iso-8859-1 strings as windows-1252.
And what's the performance trade off to always converting?
Maybe we open an issue and keep trac(k) of the problem. If more people have the same issue, then we should think about fixing it. My proposal in this case would be to tell them [the event organizer] that there's an obvious flaw in their mailings which prevents their customer from viewing it.
I personally don't really want to fix other people's issues and make RoundCube slower. Doesn't sound like win, win. ;-)
If you think about it, there's not really a performance penalty to interpreting iso-8859-1 text as windows-1252. The only difference is that if a character in the range 0x80-0x9F is encountered in the text, that character is re-encoded in the UTF-8 equivalent of the windows-1252 character. If no characters are encountered in that range, there is no difference in behavior.
I'm starting to like that option, despite it being a deliberate workaround for rule-breakers!
-Eric
List info: http://lists.roundcube.net/dev/