I can bring you up to date on what has happened.
The project was previously edited with H&M 4.1 with HTML output set to legacy encodings (ISO-8859-1 + entities), and each page began with
Code: Select all
<?xml version="1.0"?>
...
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
Using H&M 4.51 the code begins with exactly the same lines but text is saved as Windows-1252 and is not rendered correctly.
If Export UTF-8 encoded HTML is then ticked each file then begins:
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
...
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
All characters are displayed correctly as intended but if IE6 users try to view the pages over HTTP behind our corporate firewall the message above is output. Viewing local files with IE6 or using IE7 or Firefox are not problems. This was reported with H&M 4.1 and we worked round this by using legacy encodings. This is probably the most serious issue for us and I am now wondering whether if it is really a bug in Help & Manual or some sort of network configuration issue.
If I then revert to legacy encodings the files begin:
Code: Select all
<?xml version="1.0" encoding="Windows-1252"?>
...
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
This renders all characters correctly but also has the IE6 issues described above.