Cart
[Home] [By Thread] [By Date] [Recent Entries]
Changing the encoding in the output method node does not seem to affect the meta tag inserted by MSXML right after the head, as long as the output method="html". As I said earlier, it can be overridden by adding a response.charset at the top of the ASP page. The meta tag still appears, but presumably IE ignores the meta tag if the charset is explicitly defined in the http header. The other alternative, as Thomas Nielsen pointed out, is to change the output method to xml, and add the meta node into the result document after the transformation. The downside of this, in my opinion, is that the method="html" output text is nicer to read and easier to debug, not a production issue, but for development its a PITA. Adding any whitespace to the document with output=xml (eg, indent="yes") sometimes changes the way the browser renders the page. The question then, is MSXML 3.0 broken because it adds the meta node into the result set if output method="html"? XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
