[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Safe-guarding codepoints-to-string() from wrong in
Florent Georges wrote:
The intent of XSLT transformations is not to work with characters, but with the data model defined in [XDM]. Of course, there are a lot of functions to operate on strings, but dealing with the codepoints directly in the stylesheet is not a frequent thing IMHO. I understand that. But with the advent of unparsed-text() and related functions, plus removing the necessity of having an input document, XSLT opened up a whole new world of applications of data transformations. As a matter of fact, I find myself working daily doing transformations of legacy text-based data formats. But I'm aware of the discussions that have been in the past about XML compliant data and if XSLT should be able to treat non-XML characters (through unparsed-text() or otherwise). For this version, partly for security reasons (buffer overflow etc), it was decided against facilities for non-XML compliant data. Unfortunately. Perhaps in a next version (in another decade?). 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
|