<s3 title="Open bugs and bug reporting">
<p>Open bugs:</p>
<ul>
<li>When format-number() should format NaN or infinity, it generates the wrong string if default strings are used. <em>Workaround:</em> declare the strings in an xsl:decimal-format instruction at the top of the stylesheet.<br/><br/></li>
<li>A "not serializable exception" occurs when you attempt to run a precompiled stylesheet that expects parameter values to be passed in. If you encounter this problem, you should forego the use of precompiled stylesheets until a fix is available.<br/><br/></li>
<li>The namespace::* axis only selects namespaces that were declared locally on the context node. Inherited namespaces are in effect; the only known flaw is the lack of their presence on this rarely-used axis. The name() function, when applied to a namespace node, returns a string that disagrees with other processors, and the XPath spec is vague on this point.<br/><br/></li>
<li>Implied HTML output (the output begins with &lt;HTML&gt;, but the output method has not been explicitly set to HTML) is not thread-safe, due to a "late" change of output method. <em>Workaround:</em> put an explicit &lt;xsl:output method="html".../&gt; declaration in the stylesheet.<br/><br/></li>
<li>In some cases, exclude-result-prefixes takes effect even when the specified prefix appears in sub-elements, causing output of unresolved prefixes. If you experience this, please adjust your exclude-result-prefixes attribute.<br/><br/></li>
<li>The id() function doesn't work in some complex match patterns.<br/><br/></li>
<li>If you specify HTML output and encoding via xsl:output, and if a &lt;HEAD&gt; element is generated, then the encoding should be represented in a &lt;META&gt; tag inside the &lt;HEAD&gt; element. We do not put out the META tag nor any representation of the encoding in this case.<br/><br/></li>
<li>If you are generating processing instructions (PIs) in XML output, and you attempt to insert a literal "?>" in it, the spec says that "? >" should be generated, inserting a space to prevent interpretation as the end of the PI. We do not take this special step, so "?>" is generated.<br/><br/></li>
<li>When outputting URI attributes in HTML, almost all "control" characters below decimal 32 will cause an error to be raised, rather than silently being discarded. Most characters above decimal 127 will be output as that character. Percent should be output as %25 at all times (it is currently output as a literal percent); this will be fixed later.<br/><br/></li>
<li>Need to verify which HTML element attributes should be treated as URIs.<br/><br/></li> 
<li>The setDiagnosticsOutput() method does not cause redirection of all the diagnostics that should be affected.<br/><br/></li>
<li>If the use of an attribute value template for output (for example, attrib="{@title}") generates incorrect characters above decimal 127, try using the "long form" instead (for example, &lt;xsl:attribute name="attrib" select="@title"/&gt;).<br/><br/></li>
<li>When using document() with two arguments, the second attempting to (re-)establish the base in the input document, the form document(<ref>x</ref>,/) may raise an error. <em>Workaround:</em> Use document(<ref>x</ref>,/<ref>doc</ref>) where <ref>doc</ref> is the outermost element of the input document.<br/><br/></li>
<li>Attribute sets and document() references in imported stylesheets should be global, but are not.<br/><br/></li>
<li>A variable can be declared with a qualified name(for example, my:var), but later attempts to reference it (for example, $my:var) may crash<br/><br/></li>

</ul>
<p>Bug reports that we have not yet confirmed:</p>
<ul>
<li>We have a report that passing a long string value (somewhere over 128 characters) to a template via with-param caused an overflow problem under Solaris with a Sun JDK. We have not seen the problem under Sun's JDKs (1.1.8 and 1.2.2) on Win32. Additional reports are welcome.<br/><br/></li>
<li>We have a report that external entities can affect xsl:copy in a DOM input scenario. An external entity that had no attributes was causing improper copying, and adding an attribute fixed the problem. To date we have been unable to create the bug situation in our lab.<br/><br/></li>
</ul>
  <p>The Apache XML Bug Tracking System is currently not working. If you find a bug, please report it (with "Xalan-J 1 bug" in the subject line) to the <human-resource-ref idref="xalandev"/>.</p>
</s3>


