Saxonica Developer Community

2019-07-18

• 
  Debbie Lockett Saxon

  19:30 · Commented on issue

  Committed in build99 and build100: add run of tag link checker stylesheet (check-tag-links.xsl) to jd-build as part of product-xsljavadoc target; also updated stylesheet to produce diagnostic messages to highlight issues (as well as in t... Bug #4258: Checking for broken tag links in javadoc

  Following on from work investigating forum topic 7505 (https://saxonica.plan.io/boards/3/topics/7505), it would be good to be able to check that the links generated from `{@link}` markup in javadoc comments will work.
  As noted in the...
• 
  Debbie Lockett Committed changes to Java source on 9.9 and 10.0 branches, to fix some problematic links as highlighted using the check-tag-links.xsl stylesheet.

  18:54 · Commented on issue
• 
  Debbie Lockett I have created a stylesheet jd-build/check-tag-links.xsl to check tag elements in javadoc-xml/packages/ files against javadoc-types.xml. This should be run after regenerating the content of javadoc-xml (product-xsljavadoc build task), an...

  18:48 · Edited issue
• 
  Debbie Lockett Following on from work investigating forum topic 7505 (https://saxonica.plan.io/boards/3/topics/7505), it would be good to be able to check that the links generated from `{@link}` markup in javadoc comments will work.
  As noted in the...

  18:37 · Created issue
• 
  Debbie Lockett Saxon

  17:30 · Closed issue

  The problem is with javadoc-types.xml, used for javadoc searches, as generated by jd-build/chunk-javadoc.xsl.
  Fix in jd-build/chunk-javadoc.xsl stylesheet committed on 9.9 and 10.0 branches (build99 and build100).
  Regenerated javad... Bug #4257 (Resolved): Documentation javadoc search problems

  A couple more issues with the javadoc documentation search mechanism:
  1. enum constants are not included in the search results
  e.g. a search for '#ancestor' returns: the field net.sf.saxon.om/AxisInfo@ANCESTOR; the method net.sf.sa...
• 
  Debbie Lockett A couple more issues with the javadoc documentation search mechanism:
  1. enum constants are not included in the search results
  e.g. a search for '#ancestor' returns: the field net.sf.saxon.om/AxisInfo@ANCESTOR; the method net.sf.sa...

  17:10 · Created issue
• 
  Debbie Lockett Saxon

  17:00 · Replied in forum

  Indeed, by design, the package-private class net.sf.saxon.s9api.AbstractXsltTransformer is included in the XML version of the documentation, but not the HTML documentation. This is due to the fix for bug #4058. The bug problem was that m... Help: RE: http://saxonica.com/html/documentation/javadoc/net/sf/saxon/lib/OutputURIResolver.html ...

  http://saxonica.com/html/documentation/javadoc/net/sf/saxon/lib/OutputURIResolver.html says
  > and a high-level counterpart at the s9api level, AbstractXsltTransformer.setResultDocumentHandler(Function) and AbstractXsltTransformer.setR...

2019-07-16

• 
  Debbie Lockett Saxon-JS

  18:29 · Closed issue

  Updated Saxon-JS 2.0 documentation on dev trunk branch, as appropriate (i.e. add new `object` attribute for `ixsl:remove-attribute` and `ixsl:set-attribute`, update descriptions, details, and examples).
  So now marking as resolved for ... Feature #3572 (Resolved): Have an extra attribute for ixsl:set-attribute to select the element to...

  It would be nice if `<ixsl:set-attribute>` had an extra attribute so that it would not work on the current element, but on the element referenced by that attribute, much in the same way as the `object` attribute of `<ixsl:set-property>`....

2019-07-15

• 
  Debbie Lockett Saxon-JS

  16:05 · Commented on issue

  Saxon 10.0 development branch changes have been committed in the last couple of months to implement the following:
  A new option `-ns` is available on the `net.sf.saxon.Transform` command line. It can be used to specify the default nam... Bug #4176: parse-xml() in Saxon-JS loses html namespace

  To reproduce:
  1. Unzip the attached zip file, saxon-js-parse-xml-bug.zip to a directory served up by a web server.
  2. Also make Saxon-JS 1.2.0 available there
  3. Edit test.html to adjust the path to Saxon-JS
  4. Open the url to tes...

2019-07-10

• 
  Debbie Lockett Saxon-JS

  13:31 · Commented on issue

  Yes, currently there is a cardinality check that the value supplied for the `object` attribute (i.e. the result of evaluating the expression) on `ixsl:set-attribute` and `ixsl:remove-attribute` is exactly one (as for the `object` attribu... Feature #3572: Have an extra attribute for ixsl:set-attribute to select the element to be affected

  It would be nice if `<ixsl:set-attribute>` had an extra attribute so that it would not work on the current element, but on the element referenced by that attribute, much in the same way as the `object` attribute of `<ixsl:set-property>`....