Saxonica Developer Community

2024-02-14

• 
  John Lumley SaxonJS

  15:05 · Created issue

  Bug #6346 (New): NPE with replace() on SaxonJS2.6 when exported under 4.0-support conditions

  When exporting a stylesheet (either 3.0 or 4.0) for SaxonJS 2.6, using SaxonEE 12.4 running under ` --allowSyntaxExtensions:on`,
  a three-argument call on `replace()` (that is with the fourth `$flags` argument to default to the empty str...

2023-05-25

• 
  John Lumley Saxon

  19:07 · Commented on issue

  The worst I’ve had was where a bug went away when run under the debugger, due to a bug in the debugger!
  
  Sent from my iPad
  
  > On 25 May 2023, at 18:04, Saxonica Developer Community <notifications@plan.io> wrote:
  >  Bug #6051: Bug on exist() with non-existing attribute

  Maybe that's interesting:
  https://github.com/BaseXdb/basex/issues/2212

2023-05-05

• 
  John Lumley SaxonJS

  15:16 · Commented on issue

  Getting the types for function items can be pretty tricky as the arguments reverse the sense of 'subtype' (It can help to think of two sets of Venn diagrams, one in the range, i.e. function output, and on one in each of the argument doma... Bug #6011: Inline function created using xsl:evaluate

  Same bug as #6003, but on SaxonJS.

2023-04-13

• 
  John Lumley SaxonJS

  11:04 · Commented on issue

  Joel,
  The key is given in the documentation for *Compiling stylesheets using Saxon-EE* https://www.saxonica.com/saxon-js/documentation2/index.html#!starting/export/compiling-using-XJ
  where a SEF is exported using the `-ns:##html5` co... Bug #5974: SaxonJS documentation does not address namespaces

  Using the following as my guide...
  https://www.saxonica.com/saxon-js/documentation2/index.html#!browser/events
  https://www.saxonica.com/saxon-js/demos2/cities
  ...and the demo from 2021 I was unable to get the most basic interactive fu...

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...