Hello,

Thank you a lot for your answer. We are not outputting (on purpose) html in a namespace, but there are namespace declarations in the header and elsewere.

Here are the html (the bold is what makes the real difference in ie):
(We can provide the stylesheets since they are huge and proprietary, but they don't change between these outputs):

xsl output:

<xsl:output indent="yes" method="html" omit-xml-declaration="yes" encoding="UTF-8"/>


Fine html (Saxon 9.1.0.5J command line):
<html xmlns:ct="http://matrox.com/imaging/documentation/complex-tables/1.0"
      xmlns:util="http://www.matrox.com/imaging/XSLT/functions/common"
      xmlns:msxsl="urn:schemas-microsoft-com:xslt">
   <head xmlns:ms="urn:anything" xmlns:MSHelp="http://msdn.microsoft.com/msHelp">
      <title>Welcome</title>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></meta>
      <meta name="xml-files-root" content="../../"></meta>
      <meta name="manual-name" content="MIL-user-guide"></meta>
      <meta name="manual-version" content="~manual-version~"></meta>
      <meta name="generation-time" content="~generation-time~"></meta>
      <meta name="xml-timestamp" content="~xml-timestamp~"></meta>
      <link id="staticCSS" href="../../CSS Files/Matrox.Imaging.Common.css"
            rel="stylesheet"
            type="text/css"></link>
      <script language="JavaScript" src="../../JS Files/jquery-1.2.6.min.js"></script>
      <script language="JavaScript" src="../../JS Files/Matrox.Imaging.Utils.js"></script>
      <script language="JavaScript" src="../../JS Files/Matrox.Imaging.AbstractEventModel.js"></script>
      <script language="JavaScript" src="../../JS Files/Matrox.Imaging.Menu.js"></script>
      <script language="JavaScript" src="../../JS Files/Matrox.Imaging.Common.js"></script>
   </head>
   <body xmlns="" xmlns:ms="urn:anything" xmlns:MSHelp="http://msdn.microsoft.com/msHelp"
         onload="onLoad();"
         topmargin="0"
         leftmargin="0"
         class="preliminary">
      <a name="top"></a>
      <DIV ID="GeneralMenu"></DIV>
...
   </body>
</html>
------------------------------------------------------------

erroneous (saxon-B 9.1 .NET binding):
 
<html xmlns:util="http://www.matrox.com/imaging/XSLT/functions/common"
      xmlns:msxsl="urn:schemas-microsoft-com:xslt">
<head
      xmlns:ms="urn:anything"
      xmlns:MSHelp="http://msdn.microsoft.com/msHelp">
      <title>Welcome</title>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><meta name="xml-files-root" content="../../" />
      <meta name="manual-name" content="MIL-user-guide" />
      <meta name="manual-version" content="9 PP2" />
      <meta name="generation-time" content="03/11/2010 11:41:11 AM" />
      <meta name="xml-timestamp" content="06/29/2009 2:35:15 PM" />
      <link id="staticCSS" href="ms-its:MILHelp.chm::/CSS Files/Matrox.Imaging.Common.css" rel="stylesheet" type="text/css" />
 
<body xmlns="" xmlns:ms="urn:anything" xmlns:MSHelp="http://msdn.microsoft.com/msHelp" onload="onLoad();" topmargin="0" leftmargin="0" class="preliminary"><a name="top" />
<DIV ID="GeneralMenu" />
...
</body>
</html>

Thank you again for your help

 
Vincent


-----Original Message-----
From: Michael Kay [mailto:mike@saxonica.com]
Sent: Wednesday, March 10, 2010 6:08 AM
To: 'Mailing list for the SAXON XSLT and XQuery processor'
Subject: Re: [saxon] HTML Output Method differences between 9.1 and 9.2

>
> Here is the problem. Usign the HTML output method, 9.2 is closing
> empty tags like this:
> <div id="general"></div>
>
> 9.1 is closing them like this:
> <div id="general" />

This seems unlikely; I would want to see a repro providing evidence for this.

First thing is to check whether you are outputting the HTML (incorrectly) in a namespace. If you output elements in a namespace using the HTML output method, it falls back to using the XML output method.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/ saxon-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/saxon-help