- Login: johnSaxonica
- Email: firstname.lastname@example.org
- Registered on: 2013-07-04
- Last connection: 2023-07-10
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 <email@example.com> wrote:
> Bug #6051: Bug on exist() with non-existing attributeMaybe that's interesting:
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:evaluateSame bug as #6003, but on SaxonJS.
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 namespacesUsing the following as my guide...
...and the demo from 2021 I was unable to get the most basic interactive fu...
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 renderedAt 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.
Could be an interesting problem to make it asynchronous…..
Sent from my iPad
> On 12 Mar 2023, at 18:21, Saxonica Developer Community <firstname.lastname@example.org> 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.
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...
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 instructionDue 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...
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/optionsI 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...
Bug #5464 (Closed): unparsed-text() with an empty file throws a TypeErrorRunning 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...
Also available in: Atom