Configure encoding/doctype of HTML reports?

Is it possible to configure the encoding and the doctype of the generated HTML reports? Or is this a bug (whether in NCover or elsewhere)?

I'm using Thoughtworks Studios' Cruise for our CI process, and I publish HTML reports from NCover to its artifacts store; when I then view them in the web interface (in at least Firefox 3 on Windows), I see some junk characters [1]. I also see, in XML files, a leading character "Ã¯Â»Â¿" which I'm given to understand is a unicode BOM (I don't know what that is; I had the same problem with Gallio, and asked in their issue-tracker - see http://code.google.com/p/mb-unit/issues/detail?id=289 ).

I don't know whether Cruise's webserver is using the correct mime-type (that config is entirely opaque to me) to serve the files (response headers attached at [2])...?

[1] Ã¯Â»Â¿

[2] Response Headers Content-Type text/plain; charset=iso-8859-1 Content-Language en-GB Content-Length 376685 Server Jetty(6.1.6) Request Headers Host build.dev:8153 User-Agent Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3 (.NET CLR 3.5.30729) Accept text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 Accept-Language en-gb,en;q=0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive 300 Connection keep-alive Referer http://build.dev:8153/cruise/tab/stage/detail/112 Cookie JSESSIONID=18eawxs1i9221; cruise-page-intro-status=closed; t-stage-$presenter.pipelineName-RunTests=artifacts; t-stage-$presenter.pipelineName-RunCodeAnalysis=artifacts

RE: Configure encoding/doctype of HTML reports?

not possible to configure the encoding and doctype of HTML reports. Thank you for the bug report submission. I have added it to our list of issues and we will fix it as soon as we can.

Stephen Ward

RE: Configure encoding/doctype of HTML reports?

Excellent; thanks.