- Email: email@example.com
- Registered on: 2012-03-22
- Last connection: 2017-11-15
Tricky one. There are two reasons for this:
(a) on many systems, console output doesn't display the characters correctly. It's probably capable of displaying them if configured correctly, but we have no control over that
(b) errors lik... Bug #3491: In error messages Japanese characters are displayed as \uXXXXI run this demo stylesheet on the command line:
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="3.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/" élève="" 日本="">
Tom Groeneboer wrote:
> I reference the nuget version: https://www.nuget.org/packages/Saxon-HE/18.104.22.168 and the issue still exists.
> A colleague used the same application and it worked on his machine.
> This is the rep... Bug #2870: ClassNotFoundException in C#Reported by user:
I've encountered a problem while using the .NET version of Saxon-HE. We've got a .NET Core project which references Saxon-HE 22.214.171.124. If I try to run the following code:
private static readonly Processor Pr...
The proposed fix seems to work now and is committed to the Saxon 9.6 subversion branch:
Fix applied in the transform method of the TransformerImpl class. Specially, in the path where we are writing to a file we now pass the File objec... Bug #2250 (Resolved): The output file cannot be deleted after executing an XSLT transformationAfter I executed an XSLT transformation from a Java program the output file seems to be locked because it cannot be deleted.
The usual reason why this problem happens, is that the output stream over the file is not closed.
I can repr...
Create test case with the C# code provided in the Saxon9.6 Nunit test suite.
Test Case: TestTextWriterDestination() in the test set TestXsltTransformer.cs Bug #2251: NullReferenceException when transforming to TextWriterDestination [Saxon-HE 126.96.36.199]
The reason is the optimizer is trying to be too clever, it is bypassing a typecheck i nthe step.
On 15/10/2012 13:57, Robert-A.Taylor@ubs.com wrote:
> [Bug #1635]
> Hi Michael,
> Even after applying the suggested workaround we have just seen a
> similar recurrance of the issue:
> net.sf.saxon.trans.LicenseException: L... Bug #1635: Spurious error "License has expired" when multi-threadingIf two threads using the same Configuration attempt to verify the Saxon license key at the same time, a spurious error can occur: "License (serial number XXXX) has expired". The problem arises because the method to load the license file ...
Also available in: Atom