On Tue, Dec 08, 2009 at 04:11:56PM +0100, Daniel Veillard wrote:
On Tue, Dec 08, 2009 at 02:40:49PM +0000, Daniel P. Berrange wrote:
ACK, this is a better approach because it works when a browser is pointed to the HTML files locally too.
Okay, applied, this should propagate to the web site within an hour or so,
Well this didn't work, and after some debugging I found the problem. Out html.in are processed with xsltproc --html option, i.e. using the HTML parser, with default to ISO latin if out of ascii range and no meta information is provided, and the resulting .html file was correct XML (XHTML) in UTF-8 but the initil UTF-8 2 bytes were misinterpreted in the HTML parsing. The solution is to add a meta header to the news.html.in file indicating the content is UTF-8, then the proper UTF-8 HTML is generated, and I checked the Web server doesn't add any HTTP header for the encoding, so now we use UTF-8 from source to destination, and the problem should be fixed. Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/