Saxon

As well as the problem raised in the initial bug, a number of other long-standing issues with the .NET Saxon.Api documentation (many present in the documentation at least from 9.5) have been addressed:

• Various fixes for ‘type’ links - e.g. resolve ‘J’ classnames to get actual Java class name (e.g. return type JReceiver of DomDestination GetReceiver method)

• Add various missing comments - e.g. comments containing lists (e.g. Xslt30Transformer), comments with markup mistakes

• Add missing method/constructor parameters (e.g. XPathCompiler GetNamespaceURI method) - these occur when there is no documentation for the params, see the warnings produced by tohtml.xsl

• Add missing methods and properties of interfaces - e.g. IXmlLocation, IResultDocumentHandler

• Fix errors for parameters with complex types (e.g. Xslt30Transformer SetStylesheetParameters method)

• Fix errors for return types with complex types (e.g. XsltExecutable GetGlobalParameters method)

• Add missing exceptions information (e.g. XPathCompiler Compile method, XsltTransformer Run method)

• Add more tree structure for nested classes (e.g. XPathExecutable.ParameterDetails), and ‘Nested Classes’ info

• Remove ‘internal’ classes from documentation (e.g. DotNetObjectModelDefinition, WrappedExtensionFunctionDefinition)

• Add NamespaceConstant class

• Add ‘Direct known subclasses’ and ‘All known implementing interfaces’ info (see bug #1821)

Additionally, for the HTML version:

• Add protected classes (e.g. DotNetModuleURIResolver)

Committed to 9.7 (i.e. Saxon.Net in development branch, and build97)

A few more minor updates have been made, so all issues I'm aware of are now fixed.

The 9.7 documentation will be updated with the .NET release at the next maintenance release.

Bug fix applied in the Saxon 9.7.0.2 maintenance release