[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Michael Kay wrote:
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
Re: [xsl] Safe-guarding codepoints-to-string() from wrong input
Subject: Re: [xsl] 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 |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Safe-guarding codepoints-, Michael Kay | Thread | [xsl] Positional grouping with exce, Fredrik Geers |
Re: [xsl] Safe-guarding codepoints-, Abel Braaksma | Date | [xsl] Issue with copying an element, Microthunder |
Month |
Keywords