Saxonica Developer Community

2021-03-08

• 
  Philip Fearon Saxon-JS

  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...

2020-04-10

• 
  Philip Fearon Saxon

  15:09 · Closed issue

  Feature #4516 (Closed): 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...

2018-11-21

• 
  Philip Fearon Saxon

  14:10 · Closed issue

  Bug #4045 (Closed): Null pointer exception when compiling stylesheet with template containing specific XSLT instructions

  Using Saxon 9.9.0.2 professional (java), the attached saxon9902issue.xsl stylesheet fails to compile, producing the following stack trace. With Saxon 9.9.0.1, no exception is thrown.
  ~~~
  java.lang.NullPointerException
  at net.sf.saxon...

2018-05-11

• 
  Philip Fearon Saxon

  16:27 · Closed issue

  Bug #3780 (Closed): java.lang.RuntimeException: Internal error when adding a map to the final result tree

  Using Java build of Saxon 9.8.0.12.
  The development XSLT supplied here is incomplete and is flawed in the sense that it is attempting to add a map to the final result tree. I would expect some exception, but not an internal error (repr...

2015-08-31

• 
  Philip Fearon Saxon

  14:37 · Closed issue

  Bug #2450 (Closed): Unexpected result using w3c accumulator sample

  I'm learning use of XSLT 3.0 accumulators by going through the w3c examples, but I'm getting unexpected output using Saxon 9.6.0.3 PE.
  In the example 'Output Hierarchic Section Numbers' - I'm using the following input:
  ~~~
  <doc>
  <s...

2014-04-21

• 
  Philip Fearon Saxon-CE

  16:13 · Posted in forum

  When using Saxon-CE to create an XML DOM there can be a number of namsepace related issues when it comes to serializing this DOM. It becomes especially difficult to control where namespace declarations occur, some browsers even succeed i... Saxon-CE help: Sample JS code for a XMLDOM Serializer with global namespace declarations

  When using Saxon-CE to create an XML DOM there can be a number of namsepace related issues when it comes to serializing this DOM. It becomes especially difficult to control where namespace declarations occur, some browsers even succeed i...

2013-10-01

• 
  Philip Fearon Saxon

  13:02 · Closed issue

  Support #1915 (Resolved): Test case for Saxon XSLT Performance comparison

  This test case for XSLT shows a significant difference in performance for different Saxon versions
  so I thought it might be of interest. On Saxon 9.5.1.2 the test runs 90 time faster than for Saxon 9.3.1.1.
  I just ran the XSLT from th...

2013-05-21

• 
  Philip Fearon Saxon-CE

  14:06 · Replied in forum

  An alternative is to use a server-side service to act as a 'reverse-proxy' - where you append the required URL as an agrument in the HTTP request to your own server so its not cross-domain. Your own server then makes the request using th... Saxon-CE help: RE: state of the art with respect to cross domain

  whats the best idiom for dealing with pulling down data using fn:doc these days with saxon-ce ?