Saxonica Developer Community

2023-01-28

• 
  Philip Fearon Saxon

  09:48 · Posted in forum

  
  The Saxon 12 docs for the XSLT command-line options state that, for the '-m' option: 'From Saxon 11.1 this option has no effect.'
  I used to frequently use this option on the command line as follows:
  ```
  -m:net.sf.saxon.serializ... Open Discussion: XSLT command-line option '-m' - 'From Saxon 11.1 this option has no effect.'

  
  The Saxon 12 docs for the XSLT command-line options state that, for the '-m' option: 'From Saxon 11.1 this option has no effect.'
  I used to frequently use this option on the command line as follows:
  ```
  -m:net.sf.saxon.serializ...

2023-01-16

• 
  Philip Fearon Saxon

  16:34 · Closed issue

  Bug #5823 (Resolved): The implemented fn:slice function signature differs from the Saxonica docs and the specification

  Using the attached XSLT 4.0 - with extensions enabled - with SaxonJ 12.0 PE:
  When running the attached XSLT (test.xsl) from the command-line against itself I get the following error:
  ```
  Error in xsl:variable/@select on line 9 col...

2022-01-08

• 
  Philip Fearon SaxonJS

  11:37 · Closed issue

  Bug #5198 (Closed): NodeJS run from command-line with '-it:main' arg results in error when using mode="#current"

  
  This fails with SaxonJS 2.3 but the same XSLT runs OK using the Java version of Saxon. Here is the SaxonJS standard output:
  ~~~
  Saxon-JS
  2.3
  ==== Watch Variables ====
  doc: books
  
  Transformation failure: TypeE...

2021-05-20

• 
  Philip Fearon Saxon

  11:20 · Closed issue

  Bug #4996 (Closed): Namespace information missing from default XML Schema attribute added by validating XMLReader

  This issue is present in Saxon 10.5 but not in Saxon 9.8 or Saxon 9.9. It appears to be related to [issue 4993](https://saxonica.plan.io/issues/4993?issue_count=25&issue_position=3&next_issue_id=4992&prev_issue_id=4994)
  This case (sou...

2021-05-19

• 
  Philip Fearon Saxon

  12:54 · Commented on issue

  I'm checking for an inconsistency at the moment. For parsing the lexical XML, we extend `org.xml.sax.helpers.XMLFilterImpl` to gather lexical information that would otherwise be discarded by the parser. We are seeing another test failure... Bug #4993: java.lang.IllegalStateException: Prefix is bound to the wrong namespace {http://www.deltaxml.com/ns/mini-xhtml}

  This exception is thrown in Saxon 10.5 by an XSLT transform deep within our product's Java filter-chain class.
  The XML source file ([`00-2]-dxml-whitespaceDetection.xml`) for the transform (attached) has a root element in the default na...

2021-05-18

• 
  Philip Fearon Saxon

  14:49 · Commented on issue

  OK thanks, with your comment on the `-ea` switch, I understand better now why I couldn't reproduce this error outside of our TestNG environment.
  Our main objective is to ensure the tests pass with Saxon 10.n. I don't yet know quite ho... Bug #4993: java.lang.IllegalStateException: Prefix is bound to the wrong namespace {http://www.deltaxml.com/ns/mini-xhtml}

  This exception is thrown in Saxon 10.5 by an XSLT transform deep within our product's Java filter-chain class.
  The XML source file ([`00-2]-dxml-whitespaceDetection.xml`) for the transform (attached) has a root element in the default na...
• 
  Philip Fearon This exception is thrown in Saxon 10.5 by an XSLT transform deep within our product's Java filter-chain class.
  The XML source file ([`00-2]-dxml-whitespaceDetection.xml`) for the transform (attached) has a root element in the default na...

  13:18 · Closed issue

2021-03-08

• 
  Philip Fearon SaxonJS

  08:42 · Commented on issue

  This problem (using Saxon-JS 2.1), with space characters escaped to '%20' in paths, appears to affect all paths supplied in the command-line.
  For example, on macos:
  ~~~ text
  black2:saxonjs-test philipf$ node node_modules/xslt3/xsl... Bug #4925: The -s option resolves spaces incorrectly in filenames

  From https://saxonica.plan.io/boards/5/topics/8145?pn=1
  Martin Honnen writes:
  I thought I had reported a problem for Saxon JS 2.0: when I run e.g. `xslt3 -s:input.xml -xsl:sheet.xsl -t` on Windows where I am in a directory that con...

2020-04-15

• 
  Philip Fearon Saxon

  16:33 · Commented on issue

  Yes, on reflection and from what you say, I should look into other options. Specifying an errorListenerClass looks especially appealing, at least for the short-term. Longer term, a dedicated VSCode Language Server would provide much bett... Feature #4516: When using the command-line, errors/warnings to stdout give the XSLT give filename or source, but no path

  (With Saxon 10.0)
  When invoking an XSLT from the command-line, if warnings or errors are emitted to stdout/stderr, I would like to be able to uniquely identify the source file location that is the cause of the warning or error. Curre...

2020-04-13

• 
  Philip Fearon Saxon

  18:06 · Commented on issue

  OK, thanks for looking into this. The reason for this request was to allow any downloaded version of Saxon to integrate easily with the VSCode editor using an [extension TaskProvider](https://github.com/DeltaXML/vscode-xslt-tokenizer/wik... Feature #4516: When using the command-line, errors/warnings to stdout give the XSLT give filename or source, but no path

  (With Saxon 10.0)
  When invoking an XSLT from the command-line, if warnings or errors are emitted to stdout/stderr, I would like to be able to uniquely identify the source file location that is the cause of the warning or error. Curre...