Actions
Support #5601
closed
Latter defined entity is honored rather than former one in Saxon-PE 11.3
Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2022-07-13
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
Description
I'm testing Saxon-PE 10.8 and 11.3 for user project. When I convert XML file with entity reference, the former entity definition is not honored and the latter defined entity is honored in Saxon-PE 11.3.
I attached the sample file archive: diff-2022-07-13.zip
Reproducing procedure¶
- Unzip diff-2022-07-13.zip
- Maintain JDK path and Saxon-PE path in xmllist/test-pe-10.8.ps1 and test-pe-11.3-edit.ps1
- At folder xmllist, open PowerShell
- Enter command "./test-pe-10.8.ps1". This command will generate output-10.8.xml from input.xml.
- Enter command "./test-pe-11.3-edit.ps1". This command will generate output-11.3.xml from input.xml.
- Compare the both results.
My test results¶
Input XML file¶
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE book PUBLIC "-//AHF//DTD J2008 4.2-based AHF XML DTD for SM//EN" "ahfsm2-4.dtd">
<book>
Ohm=&ohrm;
</book>
Entity definition¶
Entity ohrm is defined in iso-num.ent and AHFproc.ent.
iso-num.ent
<!ENTITY ohrm "Ω"> <!-- OHM SIGN -->
AHFproc.ent
<!ENTITY ohrm "Ω"> <!-- Omega -->
Also AHFproc.ent is written after iso-inum.ent.
ahfsm2-4.dtd
<!ENTITY % ISOnum PUBLIC "ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML" "iso-num.ent">
%ISOnum;
...
<!ENTITY % AHFproc PUBLIC "-//AHF//ENTITIES for Process//EN//XML" "AHFproc.ent">
%AHFproc;
Output results¶
output-10.8.xml (The former defined one is adopted)
output-11.3.xml (The latter defined one is adopted)
I think that Saxon-PE 11.3 does not conform XML entity definition rule: the first defined one will be adopted. If there is my misunderstanding, please let me know.
Regards,
Files
Please register to edit this issue
Actions
.