Debbie Lockett
- Login: deblock
- Email: debbie@saxonica.com
- Registered on: 2014-03-13
- Last connection: 2022-05-27
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 6 | 253 | 259 |
Reported issues | 6 | 125 | 131 |
Projects
Project | Roles | Registered on |
---|---|---|
Saxon | Manager, Developer, Reporter | 2014-04-04 |
Saxon-CE | Reporter | 2014-04-04 |
SaxonC | Manager, Developer, Reporter | 2014-04-04 |
SaxonJS | Manager, Developer, Reporter | 2016-08-11 |
SaxonMirrorHE | Manager, Developer | 2021-02-02 |
Activity
2022-05-27
-
I've added nodejs unit tests for destination `document`. Currently this returns each secondary result document wrapped in an array (the result sequence from the builder), rather than just the document node directly. So that should be fix... Bug #5493: Problems with transform result output.resultDocumentsAs raised by Martin in the forum (see message#8725), the transform results object `resultDocuments` property is not being populated as intended when `deliverResultDocument` requests the `destination` to be `serialized`.
There is some ... -
2022-05-25
-
I'm moving the "Writing to ..." processing message for secondary results which is currently output when the destination is "file" or "serialized". If the `deliverResultDocument` `save` function is not writing to file store, I find this m... Bug #5493: Problems with transform result output.resultDocumentsAs raised by Martin in the forum (see message#8725), the transform results object `resultDocuments` property is not being populated as intended when `deliverResultDocument` requests the `destination` to be `serialized`.
There is some ... -
2022-05-24
-
Added nodejs unit tests saxonapi `async-trans-031` and `async-trans-032`.
Code fixes committed on saxonjs2 and main branches, to use default save function which saves to `output.resultDocuments` when the `deliverResultDocument` functi... Bug #5493 (In Progress): Problems with transform result output.resultDocumentsAs raised by Martin in the forum (see message#8725), the transform results object `resultDocuments` property is not being populated as intended when `deliverResultDocument` requests the `destination` to be `serialized`.
There is some ...
2022-05-17
-
Thanks for raising this. I've now opened a bug to look into the problems, please see ##5493
When `deliverResultDocument` is not supplied at all, actually I do not expect `resultDocuments` to be populated since the default for `deliver... General: RE: resultDocuments property of transform call result not populated?I have revisited the population of the `resultDocuments` property of the result of the `transform` Saxon-JS API function with 2.4 under Node.js but I still don't see it populated.
According to the documentation https://www.saxonica.co... -
Bug #5493 (In Progress): Problems with transform result output.resultDocumentsAs raised by Martin in the forum (see message#8725), the transform results object `resultDocuments` property is not being populated as intended when `deliverResultDocument` requests the `destination` to be `serialized`.
There is some ...
2022-05-12
-
Bug fix applied in the SaxonJS 2.4 maintenance release. Bug #5471 (Closed): Results object from asynchronous SaxonJS.transform does not contain stylesheetInternalAs raised by Martin in a forum post a few months ago (https://saxonica.plan.io/boards/5/topics/8296): the results object contains `stylesheetInternal` from a synchronous `SaxonJS.transform` call, but not from an asynchronous one. Belated...
-
Bug fix applied in the SaxonJS 2.4 maintenance release. Feature #5462 (Closed): Add "-relocate" command line option for XX compiler (xslt3 package)The `-relocate` command line option is provided for use when exporting SEFs with SaxonEE, but this option is not currently provided with the SaxonJS xslt3 command line package. It would be useful to add it.
Currently all XX-compiled S... -
Bug fix applied in the SaxonJS 2.4 maintenance release. 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