- Email: firstname.lastname@example.org
- Registered on: 2014-03-13
- Last connection: 2021-05-14
Marking resolved, as the tests are no longer failing. Bug #4768 (Resolved): fn:transform(): source-node and global context itemThe specification of fn:transform() states:
When source-node is supplied then the global-context-item (the context item for evaluating global variables) is the root of the tree containing the supplied node.
Test case fn-transform-...
JS unit tests ixsl/setStyle20 and setStyle21 ported over to new Selenium testing framework (mochaBrowserTests).
Code fix committed in XX compiler in ixsl.xsl, to ensure that xpath-default-namespace is included on IXSL extension instru... Bug #4641 (Resolved): xpath-default-namespace not being honoured on ixsl:*/@objectI've had a couple of cases where the XPath expression in the `object` attribute of ixsl instructions needs specific namespace bindings (i.e adding a prefix) rather than defaulting to the `xpath-default-namespace` in scope, using the XX ...
Documentation updated to match what is currently implemented, i.e. :
1. Added documentation for the `xsl:source-document` attributes `saxon:dtd-validation`, `saxon:expand-attribute-defaults`, and `saxon:xinclude` (at /xsl-elements/so... Bug #3995: Undocumented and untested extensions to xsl:source-documentThe 9.9 implementation of xsl;source document includes code to implement a number of extension attributes which appear (as far as I can tell) to be undocumented and untested. These include:
saxon:dtd-validation=yes|no - controls wheth...
The four URI query parameters that are available for use with the `doc()` function are: `validation`, `strip-space`, `parser`, and `xinclude`.
Committed updates to the documentation source on Saxon 10 and trunk branches:
* `xinclud... Bug #4466 (Resolved): Documentation on XInclude processingThe page at https://www.saxonica.com/documentation/index.html#!sourcedocs/XInclude doesn't mention the possibility of requesting XInclude processing using query parameters on the URI.
The page at https://www.saxonica.com/documentation...
Documentation source updated on Saxon 10 branch. Bug #4868 (Resolved): Documentation of xsl:result-documentAt https://saxonica.com/documentation/index.html#!xsl-elements/result-document it is stated
> The xsl:result-document instruction may also take the extension serialization parameter saxon:indent-spaces.
But there is no mention ...
`XsltTransformer.GetUnderlyingDestination()` reinstated so that EEN builds. Otherwise get failure (in gradle build task een_csharpApi):
error CS0535: `Saxon.Api.XsltTransformer' does not implement interface member `Saxon.Api.XmlDestin... Bug #4883: .NET API - misspelt property name - XsltTransformer.ImplemmentationProperty name `XsltTransformer.Implemmentation` should be `XsltTransformer.Implementation`
Reopening. I believe match-265, match-267, match-269 pass; but match-266 and match-268 still fail. Bug #4755 (In Progress): Pattern x/(a|b) is rejectedSee bug #4645.
The new tests added for bug #4645 (for Saxon-J) are failing on Saxon-JS: specifically match-266 and match-268.
Fix committed on the saxon10 branch. Saxon 10 documentation updated online (HTML and XML versions). Support #4874 (Closed): Documentation: Java extension functions: full interface
The infobox on Java extension states
On Saxon-PE and Saxon-EE this can conveniently be done by declaring them in a configuration file
implying that HE can't configure extension functions from a configuration file. This pro...
Very belatedly marking fixed in Saxon-JS 1.2.0 maintenance release. Bug #3905: Incorrect casting of xs:untypedAtomic in XDMString.compareTo()In Atomic.js `XDMString.compareTo()` casts strings that are untypedAtomic to the other operand type. This is in line with the semantics of General Comparisons for operators such as <. However, evaluation of `gc` already performs that ...
Also available in: Atom