Saxonica Developer Community

2024-07-25

• 
  Norm Tovey-Walsh Saxon

  10:49 · Commented on issue

  https://github.com/qt4cg/qtspecs/issues/1347 Bug #6488: Should the escape-solidus option apply to xml-to-json?

  At the moment, it appears only to apply to serialization.

2024-07-24

• 
  Norm Tovey-Walsh SaxonJS

  18:34 · Closed issue

  Now that SaxonJ supports the `escape-solidus` option, it seems practical to add it here as well. I've added support for the `escape-solidus` option to the `serialize()` function (when using `method="json"`) and the `xml-to-json` function... Support #5225 (Resolved): While using xslt 3.0 function "xml-to-json" would like to avoid escaping '/'

  We are trying to convert xml to json, while using function "xml-to-json" it is trying to escape '/' by adding '\' before it. We would like to avoid doing that and translate as is.
  ~~~ xml
  <?xml version="1.0" encoding="UTF-8"?>
  <xs...
• 
  Norm Tovey-Walsh Saxon

  17:59 · Created issue

  Bug #6488 (New): Should the escape-solidus option apply to xml-to-json?

  At the moment, it appears only to apply to serialization.
• 
  Norm Tovey-Walsh SaxonJS

  15:10 · Commented on issue

  I don't recall what observation was the impetus behind logging this bug. (Always log a test case, Norm.)
  However, in SaxonJS 3.x, it will be possible to register an XSLT function as the event handler for a non-bubbling event. At the m... Bug #5572: Scroll events in a grid don't bubble up to the document

  If we don't address the issue of non-bubbling events, we should document this.

2024-07-23

• 
  Norm Tovey-Walsh Saxon

  19:31 · Closed issue

  Fixed. Bug #6487 (Resolved): The SEF checksum generated by Saxon 12.5 will not work with SaxonJS 2.x

  Saxon 12.5 introduced a cryptographic hash to SEF files (in addition to the existing, adaptive CRC hash already present).
  Unfortunately, the Saxon 12.5 hashing algorithm fails to include the new, cryptographic hash in its computation ...
• 
  Norm Tovey-Walsh Saxon 12.5 introduced a cryptographic hash to SEF files (in addition to the existing, adaptive CRC hash already present).
  Unfortunately, the Saxon 12.5 hashing algorithm fails to include the new, cryptographic hash in its computation ...

  19:19 · Closed issue
• 
  Norm Tovey-Walsh SaxonJS

  11:00 · Closed issue

  I've added support for the `indent` option. It's not exactly what JavaScript does when asked to produce indented JSON, but it certainly introduces sufficient line breaks and indentation to be readable. Feature #4991 (Resolved): Do indentation of JSON with xml-to-json($json-xml, map { 'indent' : true() })

  The function `xml-to-json` takes an optional second argument with a map for options, the one being defined is a boolean value for the key `indent`.
  While the Java and .NET product honour that option and do indent any produced JSON, Sa...

2024-07-22

• 
  Norm Tovey-Walsh Saxon

  18:22 · Closed issue

  I believe this has been resolved in XML Resolver 5.2.4 or later. (It will also have been resolved in 6.0.4 or later when that's published, but that's not relevant today.) Bug #6474 (Closed): IllegalArgumentException attempting to resolve a Windows URI with backslashes

  See https://github.com/xmlresolver/xmlresolver/issues/184
  ```
  When I use 5.2.3 with Saxon, I got the IllegalArgumentException shown below. This prevents to
  upgrade Saxon to 12.5.
  PS D:\My_Documents\XML2021\NKBJ\proj\ymc-xml-to-pd...

2024-07-19

• 
  Norm Tovey-Walsh SaxonJS

  18:07 · Commented on issue

  Indeed, the implementation of `xml-to-json` diligently checks that the `indent` option is a `boolean` then...never mentions it again. :-( Feature #4991: Do indentation of JSON with xml-to-json($json-xml, map { 'indent' : true() })

  The function `xml-to-json` takes an optional second argument with a map for options, the one being defined is a boolean value for the key `indent`.
  While the Java and .NET product honour that option and do indent any produced JSON, Sa...
• 
  Norm Tovey-Walsh SaxonJS

  16:12 · Commented on issue

  Also applied to js2 branch Bug #6417: Using xsl:mode on-no-match="skip" gives error Error XTDE0555 but should give XTSE0020

  I got sloppy when typing some XSLT 3.0 and ended up with ` <xsl:mode on-no-match="skip"/>`. While Saxon Java just tells me
  ```
  XTSE0020 Attribute xsl:mode/@on-no-match must be
  text-only-copy|shallow-copy|deep-copy|shallow-skip|...