Re: [xsl] Safe-guarding codepoints-to-string() from wrong in

Cart

XML Editor - Download a Free Trial >

See What's New >

Buy Now >

[Home] [By Thread] [By Date] [Recent Entries]

Subject: Re: Safe-guarding codepoints-to-string() from wrong input
From: Abel Braaksma <abel.online@xxxxxxxxx>
Date: Wed, 20 Dec 2006 19:17:35 +0100

Michael Kay wrote:

In Saxon, there's an internal method which should be easy enough to call as
an extension function:

<xsl:if test="nc:isXML10Valid($codepoint)"
xmlns:nc="java:net.sf.saxon.om.XML10Char">

I'll go for XML 1.0. I'll create some one-off function to treat all possibilities and assess them with Florent's functions. Using your extension function, this will quickly show how solid his solution is, and it will make it easy to adjust.

Thanks Michael,

-- Abel

Current Thread

Safe-guarding codepoints-to-string() from wrong input
- Abel Braaksma - 20 Dec 2006 14:35:05 -0000
  - Andrew Welch - 20 Dec 2006 15:08:33 -0000
    - Abel Braaksma - 20 Dec 2006 15:19:39 -0000
  - Michael Kay - 20 Dec 2006 15:20:18 -0000
    - Abel Braaksma - 20 Dec 2006 18:18:51 -0000 <=
  - Florent Georges - 20 Dec 2006 15:20:37 -0000
    - Abel Braaksma - 20 Dec 2006 18:15:22 -0000
      - Florent Georges - 21 Dec 2006 02:09:53 -0000

<- Previous	Index	Next ->
RE: Safe-guarding codepoints-, Michael Kay	Thread	Re: Safe-guarding codepoints-, Florent Georges
Re: Safe-guarding codepoints-, Abel Braaksma	Date	Issue with copying an element, Microthunder
	Month

XML Editor - Download a 15 Day Free Trial Now >

See What's New in Stylus Studio >

Buy Stylus Studio - XML Editor - Now >