Saxonica Developer Community

2019-11-22

• 
  Debbie Lockett Saxon-JS

  19:27 · Closed issue

  The Uniform Resource Identifier (URI) spec (https://tools.ietf.org/html/rfc3986#section-3.1) says:
  "Scheme names consist of a sequence of characters beginning with a
  letter and followed by any combination of letters, digits, plus
  ... Bug #4116 (Resolved): Cannot load SEF stylesheet under NW.js

  Using Saxon-JS 1.2.0, when trying to load a stylesheet in a NW.js app (v0.35.5) using Saxon-JS 1.2.0,
  the following is returned.
  ~~~
  SaxonJS.js:17943 Uncaught XError: stylesheetLocation should be absolute by now
  ~~~
  After diggin...
• 
  Debbie Lockett Saxon

  17:31 · Commented on issue

  Fix committed on 9.9 and trunk branches, as described above. (i.e. In Compilation.satisfyPackageDependencies(), set the target edition for the PackageLibrary from the target edition of the Compilation's compilerInfo.)
  Leaving the bug ... Bug #4391: Cannot find a 0-argument function named {http://saxonica.com/ns/interactiveXSLT}page()

  Using <oXygen/> XML Editor 21.1, build 2019101513 and its in-menu *Tools > Compile XSL Stylesheet for Saxon...* command.
  *About > Libraries* claims Saxon EE 9.8.0.12.
  In preview the following XML code seems to be partially eaten b...
• 
  Debbie Lockett Rather than compiling within Oxygen, I've run some tests to compile the supplied files from the command line. e.g. using:
  ~~~
  -nogo
  -target:JS
  -xsl:root.xsl
  -config:saxon.conf.xml
  --generateByteCode:off
  -export:root.sef
  -t
  -r...

  15:42 · Commented on issue

2019-11-12

• 
  Debbie Lockett Saxon

  16:47 · Commented on issue

  Re Note #4334-1 above, changes have been committed to remove the unnecessary "?" indicators: style/elements-body.xsl stylesheet fix, and generated extensions/output-extras/serialization-parameters page updated. Fix committed on 9.9 and 1... Bug #4334: Undocumented serialization property saxon:unfailing

  The serialization property saxon:unfailing is used internally when the XML or JSON output methods are invoked from the adaptive output method, to suppress all serialization errors.
  There's nothing to stop the property being set direct...

2019-11-05

• 
  Debbie Lockett Saxon

  12:37 · Created issue

  Bug #4373 (New): Documentation: Implementation-defined aspects of Serialization

  The Serialization Conformance information in the Saxon documentation at http://www.saxonica.com/documentation/index.html#!conformance/serialization is out of date. It refers to the XSLT and XQuery Serialization 3.1 Recommendation dated 2...

2019-09-05

• 
  Debbie Lockett Saxon

  16:10 · Closed issue

  Bug #4307 (Resolved): .NET API Documentation: type hierarchy for XdmNode does not show XdmValue a...

  In the .NET API Documentation, the type hierarchy for `XdmNode` is shown as
  ~~~
  System.Object
  Saxon.Api.XdmItem
  Saxon.Api.XdmNode
  ~~~
  The fact that `XdmItem` is a subclass of `XdmValue` is not shown; although on the page f...
• 
  Debbie Lockett Saxon

  12:11 · Closed issue

  Various changes have been made in the .NET samples to get them working correctly. Fixes committed on the 9.9 and 10.0 dev branches.
  The latest9.9/hen/csource/samples directory has been removed, as suggested above, to avoid duplication... Bug #4299 (Resolved): Saxon-HE v9.9.1.4 Exception XPDY0002 running .NET C# test example XsltSimple1.

  Saxon-HE v9.9.1.4 Exception XPDY0002 running .NET C# test example XsltSimple1.
  I am using Saxon API for .NET (Saxon-HE v9.9.1.4 version). I am testing on Windows 10 Enterprise 1809 with Visual Studio Professional 2019 version 16.2.0.
  ...

2019-09-04

• 
  Debbie Lockett Saxon

  13:42 · Edited issue

  Changes committed on 9.9 and 10.0 branches in MyDotNet/doctools/merge.xsl and convert-to-jel-package.xsl, to produce full type hierarchy (rather than just 1 or 2 level hierarchy).
  The 9.9 documentation will be updated online with the ... Bug #4307 (In Progress): .NET API Documentation: type hierarchy for XdmNode does not show XdmValu...

  In the .NET API Documentation, the type hierarchy for `XdmNode` is shown as
  ~~~
  System.Object
  Saxon.Api.XdmItem
  Saxon.Api.XdmNode
  ~~~
  The fact that `XdmItem` is a subclass of `XdmValue` is not shown; although on the page f...

2019-09-02

• 
  Debbie Lockett Saxon

  14:20 · Closed issue

  This support issue has been rather neglected, but I would like to close it. As I understand it, the issue is about understanding the .NET samples. The user requests "step-by-step instructions on how to use the C# sample code examples wit... Support #2612 (Resolved): VS2010 .NET Assemblies and Sample Code - More Instructions Needed

  This issue was raised over 9 years ago and I can't find any specific updates or guidance to clarify the questions that were asked previously.
  https://saxonica.plan.io/boards/3/topics/3876
  Could someone on the support team subm...
• 
  Debbie Lockett Saxon

  12:28 · Closed issue

  Bug #4258 (Resolved): 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...