Project

Profile

Help

Bug #5649

closed

xmlresolver does not handle repeated whitespace in public identifiers when using xml catalog

Added by Martin Latterner over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Low
Category:
Resolvers
Sprint/Milestone:
-
Start date:
2022-08-17
Due date:
% Done:

0%

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

Description

Please see the attached zip file.
I have there an xml file and a catalog. The public identifiers in both the xml and the catalog contain a doubled whitespace.

Saxon 11.2 is unable to parse the XML:

[latternm@somwhere saxon11catalog]$ java -jar /path/to/saxon-ee-11.2.jar -s:xml.xml -xsl:xsl.xsl -catalog:catalog.xml 
I/O error reported by XML parser processing file:/home/latternm/saxon11catalog/xml.xml: /home/latternm/saxon11catalog/main.dtd (No such file or directory)

When I add an entry into the catalog with the whitespaces collapsed, then it works.

I think the resolver normalizes (collapses) whitespace in the input, but not in the catalog.

Of course, we can work around this problem easily, reporting it primarily because others may encounter the same issue when upgrading to saxon11.

https://www.oasis-open.org/committees/entity/spec.html

6.2. Public Identifier Normalization

In order to accurately and interoperably compare public identifiers, catalog processors must perform normalization on public identifiers in both the catalog and the input passed to them. All strings of white space in public identifiers must be normalized to single space characters (#x20), and leading and trailing white space must be removed.


Files

saxon11catalog.zip (1.08 KB) saxon11catalog.zip Martin Latterner, 2022-08-17 20:08
Actions #1

Updated by Michael Kay over 2 years ago

  • Assignee set to Norm Tovey-Walsh
Actions #2

Updated by Norm Tovey-Walsh over 2 years ago

  • Status changed from New to Resolved

Thank you. I've pushed XML Resolver 4.5.1 and XmlResolver CS 1.5.1 which fix this issue.

Actions #3

Updated by Michael Kay over 2 years ago

  • Category set to Resolvers
Actions #4

Updated by O'Neil Delpratt almost 2 years ago

  • Status changed from Resolved to Closed

Closing this bug as the bug issue has been applied to the XML Resolver 4.5.1

Please register to edit this issue

Also available in: Atom PDF