- Email: email@example.com
- Registered on: 2012-02-01
- Last connection: 2018-07-09
I have committed all the above changes (a-f) on the development branch. I now need to get the 9.8 branch into shape. Bug #3843 (In Progress): Compiling an XPath expression takes 23 minutesDavid Thielen (in private email) has reported a chronic performance problem where compiling an XPath expression takes 23 minutes. The time seems to be spent in an optimization step.
(a) correct the logic for SubscriptExpression.equals()
(b) introduce a lazily-evaluated hashcode on the Expression obj...
The problem is your use of `document('')`. This expression reads the document found at the static base URI of the transformation. People often assume that it reads the stylesheet itself; but this will only be the case if the base URI of ... Help: RE: Different result between java and command line when calling named templates based on a ...Hi,
Attached I have simple test files investigating whether I could use a suggestion from Stackoverflow (https://stackoverflow.com/questions/1233702/how-to-call-named-templates-based-on-a-variable) and it seems to be working from the ...
The `AbsolutePath` object has methods allowing you to get less clunky output, e.g. `AbsolutePath.getPathUsingPrefixes()`, but the default toString() method gives the full path with all namespaces expanded, which is useful when you want t... Open Discussion: RE: Schema validation: Saxonica able return XPATH or erroneous node?Good morning,
we are using the Enterprise Edition and need - in case of a validation error - the XPATH to the erroneous node.
Is this possible with Saxonica?
Many Thanks regards
Two expressions that are actually equal are comparing not equal: the culprit is `SubscriptExpression` which uses "==" rather than "equals()" on one of the operands.
The effect is that rather than using an existing index, a new one is ... Bug #3843: Compiling an XPath expression takes 23 minutesDavid Thielen (in private email) has reported a chronic performance problem where compiling an XPath expression takes 23 minutes. The time seems to be spent in an optimization step.
The other reason is that comparing expressions is expensive e...
I found by accident that running these under XPath, the execution time is around 50s, but under XQuery, it is around 5s.
Resolution: in `CommonSubexpressionPromoter.gatherElligibles()`, treat an expression E as ineligible for promotion if E.isLiftable() returns false. Bug #3840 (Resolved): Migrating from sourceforge saxon to Saxonica Saxon-EE, problem with sorting...We are switching from sourceforge saxon 220.127.116.11 to saxonica saxon-ee 18.104.22.168.
We are having trouble with a xslt which task is to translate to a sorted xml. The same xslt, which we used against the sourceforge saxon, is given an error u...
I decided to continue indenting the paragraph end tag on the 9.8 branch in the interests of stability, but I have made the change for 9.9.
Bug #3842 (Resolved): Whitespace added before paragraph end tag in HTML serializationWith indentation enabled, using the HTML output method, the content
is serialized as
Which contravenes the serialization specification. This states (for b...
I have updated the list of inline element names to:
"a", "abbr", "acronym", "applet", "area",
"audio", "b", "basefont", "bdi", "bdo", "big", "br", "button", "canvas", "cite", "code", "data",
... Bug #3839 (Resolved): Problem with HTML5 indentation: <mark> not recognized as inline elementReported today in direct email to support(at)saxonica
I'm attaching an XSL file and HTML output which demonstrates the bug, in which — with the declaration `<xsl:output method="html" name="htmlOutput" indent="yes" version="5.0"/>` — t...
Also available in: Atom