Cart
|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Safe-guarding codepoints-to-string() from wrong input
 In some translation-stylesheet, I take user-input (arbitrary string) and replace a set of numbers to a set of characters, like this: $input = "some [34]quoted[34] string" output --> some "quoted" string <xsl:analyze-string select="$input" regex="\[(\d+)\]"> <xsl:matching-substring> <xsl:value-of select="codepoints-to-string(xs:integer(regex-group(1))" /> </xsl:matching-substring> <xsl:non-matching-substring> <xsl:value-of select="." /> </xsl:non-matching-substring> </xsl:analyze-string> Because we are talking tons of data containing the above-like strings (in text files), I'd like to make the codepoints-to-string() a bit more rock-solid. In normal operation, it fails hard. But I'd like it to gracefully degrade: be liberal in what you accept. I know that control characters are not allowed and throw an "Invalid XML character" error. Also, when adding very wide numbers (like "1234567") give a plural of the same error (Im not sure why). Some characters (I believe these are the ones that are not assigned in Unicode) result in an empty string (like "12345"). Is there a robust way of allowing/disallowing a set of codepoints (other than making one huge lookup list)? Cheers, Abel 
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
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
|
