Project

Profile

Help

Actions
Send by e-mail Copy link

Support #1354

closed

prolem with handling upper unicode characters

Added by Anonymous about 17 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Internals
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Legacy ID:
sf-1660205
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

SourceForge user: cwittern

As described in the help forum, saxon seems to have a problem handling entity references that contain upper unicode values (that is, characters with numeric codepoints larger than 65536). Two files are attached to demonstrate the problem.

Files

Download all files
test.xml (9.56 KB) test.xml Anonymous, 2007-02-15 01:36
test.xsl (9.56 KB) test.xsl Anonymous, 2007-02-15 01:37
Actions
Copy link
 #1

Updated by Anonymous about 17 years ago

SourceForge user: cwittern

Logged In: YES

user_id=222320

Originator: YES

File Added: test.xsl

Actions
Copy link
 #2

Updated by Anonymous about 17 years ago

SourceForge user: mhkay

Logged In: YES

user_id=251681

Originator: NO

You appear to have found a bug in the Xerces parser, which is the default parser in JDK 1.5. This test case works correctly with the .NET parser and with the Crimson parser (which is the default parser in JDK 1.4), but on JDK 1.5 the parser is feeding incorrect data to Saxon. Please raise the bug against the JDK. In the meantime you can work around it by selecting a different parser - Saxon will work with any SAX2-compliant XML parser. (Having said that, Xerces is usually more reliable than any other).

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF