You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org> on 2010/02/07 20:31:28 UTC
[jira] Commented: (XERCESJ-1136) Expansion fails for URIs with
non-ascii characters.
[ https://issues.apache.org/jira/browse/XERCESJ-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830752#action_12830752 ]
Michael Glavassevich commented on XERCESJ-1136:
-----------------------------------------------
Xerces has always been strict about what characters are allowed in URIs. RFC 2396 [1] does not allow non-ASCII characters in URIs unless they've been escaped. The developers have never come to a consensus on whether we should tolerate non-ASCII or not, but users are best advised to do the escaping before passing the system ID to Xerces.
Several other JIRA issues have been opened for specific cases:
XERCESJ-391 :: transformer doesn't support Chinese Name Dir
XERCESJ-420 :: Unable to locate DTD if it is in some Chinese Name Dir....
XERCESJ-825 :: Russian folder names not suppotred by SAXParser
XERCESJ-1359 :: DOMParser exception with an xml file which name contains Chinese characters
I'm going to keep this one open as the master since it describes the more general issue and return the others as duplicates.
[1] http://www.ietf.org/rfc/rfc2396.txt
> Expansion fails for URIs with non-ascii characters.
> ---------------------------------------------------
>
> Key: XERCESJ-1136
> URL: https://issues.apache.org/jira/browse/XERCESJ-1136
> Project: Xerces2-J
> Issue Type: Bug
> Components: XML Schema API
> Affects Versions: 2.7.1
> Environment: Linux, java 1.5
> Reporter: Chris Simmons
> Attachments: xercesBug.zip
>
>
> The problem appears to be that a valid anyURI that occurs, for example, in a schemaLocation attribute on an import, is not properly escaped. Any attempt to create a URI from it fails, meaning that if it is relative it is not possible to resolve it against the base system ID. MalformedURIExceptions generated are swallowed silently, and the end result is a string which is supposed to be the expanded ID which is actually not expanded. If this string is passed to an XMLEntityResolver, the entity resolver can't deal with it properly.
> I think that provided that the hint is a valid anyURI, it should be correctly escaped and the proper expanded system id calculated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org