Normally you should be able to get correct display in a case like this by just going to the View > Encoding menu of your browser and switching to Unicode UTF-8.
On Jul 22, 2015, at 2:38 AM, Marcel Schneider wrote:
> The workaround is then, if I understand well, to let web-sniffer check whether the server is forcing an unconsistent encoding:
> | Content-Type: text/html;charset=ISO-8859-1
> Then save the page...
> | meta http-equiv="Content-Type" content="text/html; charset=windows-1252"
> ...and reset the charset to the value shown in the source code:
> | meta http-equiv="Content-Type" content="text/html; charset=utf-8"
> Then open this.
>
Received on Wed Jul 22 2015 - 05:00:00 CDT
This archive was generated by hypermail 2.2.0 : Wed Jul 22 2015 - 05:00:01 CDT