Saxonica Developer Community

2023-03-13

• 
  John Lumley SaxonJS

  17:00 · Edited issue

  It looks as if, at least in Firefox and Chrome, the implict `sup` styling is being overridden by `saxon-base.css:37`, specifically setting `vertical-align:baseline` rather that `super` and `font:inherit` overriding `font-size:small`. Bug #4585 (In Progress): Documentation: superscript not rendered

  At http://www.saxonica.com/saxon-js/documentation/index.html#!conformance/xslt30, under xsl:number, we see "Saxon-JS loses precision when formatting numbers greater than 253". It presumably should be 2^53.

2023-03-12

• 
  John Lumley SaxonJS

  19:27 · Commented on issue

  Could be an interesting problem to make it asynchronous…..
  
  Sent from my iPad
  
  > On 12 Mar 2023, at 18:21, Saxonica Developer Community <notifications@plan.io> wrote:
  >
  >  Bug #5916: Using xsl:merge with xsl:merge-source for-each-source="'input1.xml'" select="some-xpath" gives error XPDY0002 "Focus for / is absent"

  I have tried to run an XSLT 3 example using XSLT 3's new xsl:merge through SaxonJS 2.5's `xslt3` command line tool under Windows 11 with Node 16, a simple example using e.g.
  ``` xml
  <xsl:template name="xsl:initial-template">
  ...

2023-03-10

• 
  John Lumley Saxon

  17:39 · Replied in forum

  On 10/03/2023 16:28, Saxonica Developer Community wrote: Help: XSLT function not compiling with SaxonC-HE 12.0 (Python)

  
  As soon as I paste the the definition of the function my:scan into the stylesheet, it does not compile ("Errors were reported during stylesheet compilation"). Without it, everything works fine (both compilation and transformation). Wha...

2022-06-19

• 
  John Lumley SaxonJS

  18:06 · Commented on issue

  You will need a mechanism to supply a function type signature, if only to establish the arity and deeper to declare types of arguments and return. Without the latter, especially for arguments, you could get any form of argument supplied ... Feature #5558: Allow clients of SaxonJS to supply a map of custom XPath functions with arbitrary names

  There's an existing mechanism whereby JavaScript functions which are in the global Window scope are automatically made available as XPath functions in a "js:" namespace, but this excludes use cases where it's desirable to add custom impl...

2022-06-14

• 
  John Lumley SaxonJS

  14:23 · Commented on issue

  Yes - this looks like an oversight - the original 'syntax check' for `xsl:copy-of` incorrectly declared the possibility of a sequence constructor child (as `xsl:copy` of course is permitted, and I assume I copy-and-pasted). Interestingl... Bug #5563: SaxonJS allows elements in supposedly empty xsl:copy-of instruction

  Due to some mental mistake I wrote some XSLT code using e.g. `<xsl:copy-of select="."><xsl:apply-templates/></xsl:copy-of>` and SaxonJS let met get away with it. When moving my code to SaxonJ, I found that it doesn't allow it and gives a...

2022-06-13

• 
  John Lumley SaxonJS

  16:36 · Replied in forum

  When originally writing the first `xslt3` command line processor I came across this quirk of Powershell requiring quoting (I was the only member of the team to do all development work on a Windows machine) and didn't find any easy worka... General: RE: Cross platform Powershell and xslt3 command line arguments/options

  I have stumbled into some oddity using SaxonJS's `xslt3` command line tool with the cross platform Powershell (aka Powershell Core): it seems I have to wrap any SaxonJS/xslt3 option in single or double quotes to get `xslt3` to parse it c...

2022-04-29

• 
  John Lumley SaxonJS

  14:19 · Closed issue

  Bug #5464 (Closed): unparsed-text() with an empty file throws a TypeError

  Running in the browser (on an older version of SaxonJS2, but I suspect not) when reading in (via an `unparsed-text()` call) an empty file, there is a TypeError thrown in `Fetch.js:checkForNonXmlChars()` . Rather than an empty string bein...

2022-04-27

• 
  John Lumley SaxonJS

  12:24 · Commented on issue

  I *think* I was the originator of this section of the code - I certainly wrote the original `fn:transform()` code. But it's probably about 3-4 years ago now, so I can't recall details I fear. But there must have been some reason to do th... Bug #5039: Chaining two XSLTs where the first creates a fragment with two element children works under Node.js but not in the browser

  When I run the code
  ~~~ javascript
  const SaxonJS = require("saxon-js")
  const xslt1Source = `<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  version="3.0"
  xmlns:xs="http://www.w3.org/2001/XMLSchema"
  exclud...

2022-02-25

• 
  John Lumley SaxonJS

  23:22 · Commented on issue

  When writing the code for the XX compiler, there are so many corner cases (many thousands of them?) that might need to be satisfied that it’s pretty much impossible to cover them all. In this case during the XPath compiling of global var... Bug #5338: XX Compiler reports "Unknown accumulator NNNNN" when an accumulator-before or -after call occurs in a global variable

  Hello, we have a pipelines and software using Saxon HE (Java) variant and the SaxonJS variant with NodeJS to build CLI tooling. We have encountered a problem in which running Saxon HE will process a collection of XSL transforms in shell ...

2022-01-11

• 
  John Lumley Saxon

  16:27 · Commented on issue

  If I read the spec correctly
  >` (//A, //B) | ()`
  should return them in document order, unless some (incorrect) optimisation has elminated the empty sequence. See https://www.w3.org/TR/xpath-31/#combining_seq Support #5200: How can I check if the nodes in any XPath result are in document order? Or put them in document order?

  Some XPath expressions, such as
  //A, //B
  do not return the nodes in document order.
  Is there a function I can call to check if the nodes are in document order? Or a function that puts them in document order?
  I use XPathSelect...