Bug #6201
closedconfiguration file: option for unparsed text URI Resolver
100%
Description
According to the documentation, one can set a custom URI resolver for unparsed-text()
and friends by setting configuration/global/@unparsedTextURIResolver
. However, I found, that this is not the right attribute name. It is configuration/global/@unparsedTextUriResolver
, i.e. URI in camel case.
Setting @unparsedTextURIResolver
has no effect, while setting @unparsedTextUriResolver
activates my custom URI resolver.
I think this is an issue of the documentation. Other attributes for setting URI resolvers use camel case and they work as documented. So fixing the docs would be consistant.
Tested on Saxon-HE 10.9 (Java). Read in docs for 10 and 12.
Link to docs: https://www.saxonica.com/documentation12/index.html#!configuration/configuration-file
Updated by Michael Kay about 1 year ago
Thanks for pointing it out.
The schema for the configuration file has the name as unparsedTextURIResolver
, but the code that reads the configuration file is looking for `unparsedTextUriResolver``
Updated by Michael Kay about 1 year ago
I think I'm going to keep the schema and the documentation using the name unparsedTextURIResolver
so that it's aligned with the property name in FeatureKeys, but change the configuration file reader to accept both the correct name (...URI...) and the one that's currently accepted.
Updated by Michael Kay about 1 year ago
- Category set to Configuration
- Status changed from New to Resolved
- Assignee set to Michael Kay
- Priority changed from Low to Normal
Fixed as suggested for 11.x, 12.x, and 13.x. The schema and documentation retain the "URI" spelling; the configuration file reader will accept either.
Updated by Michael Kay about 1 year ago
- Applies to branch 11, 12, trunk added
- Fix Committed on Branch 11, 12, trunk added
Updated by O'Neil Delpratt 12 months ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 12.4 added
Bug fix applied in the Saxon 12.4 maintenance release
Please register to edit this issue