Subject: Re: [xsl] Unicode and child element From: Colin Paul Adams <colin@xxxxxxxxxxxxxxxxxx> Date: Fri, 29 Aug 2008 12:42:04 +0100 |
>>>>> "Ken" == G Ken Holman <gkholman@xxxxxxxxxxxxxxxxxxxx> writes: Ken> The Unicode characters  through  are Ken> specifically "non-characters", which means they must not be Ken> used to represent characters in a data stream between sender Ken> and receiver. This means that two trading partners must not Ken> use them in XML documents, which makes them available for Ken> XSLT users for this character mapping technique without Ken> interfering with user data. No - they are not available for XSLT users. The author of the XSLT transformation could be considered the sender, and the XSLT processor could be considered the receiver. Non-characters can only be used in application-specific protocols which are not visible to users. So, for instance, they might be used in the internals of an XSLT processor as special markers (Saxon uses NULLs for such a purpose, as they cannot occur in XML data, but it could equally use a non-character for such a purpose). -- Colin Adams Preston Lancashire
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Unicode and child element, G. Ken Holman | Thread | Re: [xsl] Unicode and child element, David Carlisle |
Re: [xsl] Unicode and child element, G. Ken Holman | Date | Re: [xsl] Unicode and child element, David Carlisle |
Month |