[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: unparsed-text() and illegal characters

Subject: Re: unparsed-text() and illegal characters
From: Abel Braaksma Online <abel.online@xxxxxxxxx>
Date: Thu, 27 Jul 2006 21:39:21 +0200
unparsed uri
> Perhaps I'll do that.
You mean in "adding it to Saxon" as an extension? Perhaps an extension function can be used for it, like ext:replace-illegal-chars-with('FFFD')? Mmm, I guess not, probably before the data arives at the function it will already have raised an error. Or something like

ext:unparsed-uri-filter($uri, $transformFrom, $transformTo)

where $transformFrom and $transformTo are both containing hex sequences (using character entities won't work, because of this same strictness, I guess).


Michael Kay wrote:

The spec is very strict that characters not allowed in XML cause an error.
This is a change since the book was written.

However, the spec is very loose about how URIs are resolved. So a conformant
product could take the URI


as a reference to "the document formed by taking thing.txt and substituting
illegal characters with xFFFD."

Perhaps I'll do that.

Michael Kay

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.