Subject: [xsl] XSLT2 Character Maps From: "Christian Roth" <roth@xxxxxxxxxxxxxx> Date: Sat, 24 Jul 2004 13:54:05 +0200 |
Hi, I've had a look at XSLT 2's character maps feature. In the tool I am working on (upCast from infinity-loop), we have that very concept implemented now for several releases and added some convenience options (like the ability to easily define a range of Unicode positions that should be output as numerical decimal/hexadecimal entities) - but that's not the issue here. The point is that we resp. some of our users also use character maps to create (mainly empty) elements in the output. For example a line in our maps like 0x2028="<linebreak/>" creates a linebreak element in the output for every instance of Unicode character 
. The problem that arises for us is attribute values: If these contain a 0x2028 character, they get malformed: <element attr="a
b"> gets <element attr="a<linebreak/>b">, which is not valid XML.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Converting a Batch File t, David . Pawson | Thread | RE: [xsl] XSLT2 Character Maps, Michael Kay |
RE: [xsl] Multiple level filtering , Jeff Cann | Date | RE: [xsl] XSLT2 Character Maps, Michael Kay |
Month |