> So... I took a look at this issue, and actually, i'd say the bug is the > other way around. The previous behaviour was not exactly to fallback to > windows-125x, but rather to interpret iso-8859-x as windows-125x... If > you look which encoding is selected when "correctly" displaying the > page, you'll see it's iso-8859-1, which is wrong. > > That will be a wontfix for me. I'm not going to makecbe > interpreted as windows-1252...
I understand, but countless sites do get it wrong: they do use windows-1252 characters even when declaring iso-8859-1. When testing on Firefox or IE the site authors don't see a problem, so (epiphany) users like me are forced to change the encoding manually every time. It's a bit tedious to manually change the encoding for every other site I try to look at. That's why I'd like to ask you to please reconsider. Thanks, -- M -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]