Re: unparsed-text() and illegal characters

Play the video

Subject: Re: unparsed-text() and illegal characters
From: Abel Braaksma Online <abel.online@xxxxxxxxx>
Date: Thu, 27 Jul 2006 21:39:21 +0200

> 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).

Cheers,
Abel

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

thing.txt?substitute-illegal-chars=FFFD

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

Perhaps I'll do that.

Michael Kay
http://www.saxonica.com/

Current Thread
unparsed-text() and illegal characters Abel Braaksma Online - 27 Jul 2006 18:11:00 -0000 Michael Kay - 27 Jul 2006 19:22:06 -0000 Abel Braaksma Online - 27 Jul 2006 19:39:42 -0000 <=

<- Previous	Index	Next ->
RE: unparsed-text() and illeg, Michael Kay	Thread	Highlighting words/phrases, yguaba
RE: unparsed-text() and illeg, Michael Kay	Date	Re: Removing Blank pages from, J.Pietschmann
	Month

Back To School Sale!

Save 30% off all Stylus Studio 2008 Products when you purchase from our Online Shop.

Offer ends August 31, 2008.

Coupon Code
TRTY-C4JV-OFF

Download The World's Best XML IDE!

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

Subscribe in XML format

RSS 2.0
Atom 0.3


	Stylus Studio® Developer Network \| Contact Us \| Email this page