O'Neil Delpratt
O'Neil Delpratt- Email: oneil@saxonica.com
- Registered on: 2012-01-26
- Last connection: 2020-07-09
Issues
- Assigned issues: 48
- Reported issues: 299
Projects
Activity
2020-07-09
-
Hi Ofer,
Thanks for reporting this issue. This may be similar to the bug issue #4467.
Just to add to Mike's post in comment 2. Encoding/decoding can become confusing if the text supplied into Saxon is not of the format that the use... Support #4638: Output xsl3 transform to UTF-16LE with BOMHi all,
I'm testing Saxon/C with C++ (version PE). While transform without <xsl:output> create file encoded with UTF-8, trying to output to UTF-16LE (windows) with <xsl:output encoding="utf-16le" byte-order-mark="yes"/> create output en...
2020-06-27
-
Bug #4617 (New): macOS Catalina error: “libsaxonpec.dylib” cannot be opened because the developer cannot be verified.I tried to run the sample C++ program with Saxon/C on macOS Catalina 10.15.4. Getting the following error:
~~~
macOS Catalina error: “libsaxonpec.dylib” cannot be opened because the developer cannot be verified.
~~~
There is an u...
2020-06-22
-
Bug #4609 (New): Lack of documentation to package Saxon/C C++ in third-party systemsThis bug is created as a result of a user enquiry.
There seems to be a lack of documentation on how to package Saxon/C C++ API in a third-party system. There needs to be a clear guide to say what needs building in advance to create th...
2020-06-16
-
Bug fixed and committed to subversion available for the next release. I have also attached the files: Transform.c, Query.c and Validate.c for users to pick up the patch in their current Saxon/C installation. Bug #4595 (Resolved): commands library paths not customizableFrom the resolution of the bug issue #4594 I discovered that from the Saxon/C command-line interfaces there is no way to customize the location of the Saxon/C library from the defaults.
I have copied the same logic of the code in the ... -
From the resolution of the bug issue #4594 I discovered that from the Saxon/C command-line interfaces there is no way to customize the location of the Saxon/C library from the defaults.· Closed issue
I have copied the same logic of the code in the ... -
Windows bat script created and added to subversion. Also adding the files to the bug issue for users to download.
I did notice that path locating of the Saxon/C library is not customizable as in the C++ API. I have fixed this problem ... Bug #4594 (Resolved): build file for command interface not available on WindowsReported by user:
The build file for command interface not available on Windows. The counterpart is present for unix systems (e.g. command/buildeec-command.sh).
2020-06-15
2020-05-14
-
-
Bug #4550 (Closed): Embedded license key for xpath-functions.scm has expiredThe compiled schema module `xpath-functions-scm` in 10.0 was inadvertently produced using an embedded license key that had a 30-day expiry, meaning that it no longer functions.
The module is used (for example) when `fn:analyze-string(... -
Also available in: Atom
.