On 5/24/05, Michael Kay <mike(_at_)saxonica(_dot_)com> wrote:
Why would you want to do it? The encoding isn't supposed to contain any
information apart from telling you what the encoding is, which you don't
need to know once the document has been parsed.
Michael,
Why was this decision made? I see from the XSLT 2.0 requirements
document, that one of the requirements was to give XSLT the ability to
figure out what the input encoding was. There is even a use case
mentioned in the requirements document :
http://www.w3.org/TR/xslt20req (see item 1.4) which talks about why
this would be useful.
Thanks,
Kenneth
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--