6186 2008-10-28 10:56:23 +0000 [XSLT 2.0] References to Unicode specification 2010-08-08 21:39:20 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 2.0 Recommendation PC Windows NT CLOSED FIXED P2 normal --- 1 mike mike public-qt-comments oldest_to_newest 22263 0 mike 2008-10-28 10:56:23 +0000 In the description of xsl:number (section 12.3) there are references to Unicode character categories and the Unicode character properties database. There are no entries in the References section to indicate precisely what these refer to, in particular nothing about which Unicode version(s) are used. 23351 1 mike 2009-01-30 10:55:54 +0000 This was discussed by the XSL WG on 2009-01-29. The result was the following action: Action A-2009-01-29-003: [Bug 6186] Michael Kay to investigate how XPath and F&O handle references to Unicode character properties and character properties database, and propose aligning XSLT with them. XPath 2.0 has in its normative references: Unicode The Unicode Consortium. The Unicode Standard Reading, Mass.: Addison-Wesley, 2003, as updated from time to time by the publication of new versions. See http://www.unicode.org/unicode/standard/versions for the latest version and additional information on versions of the standard and of the Unicode Character Database. The version of Unicode to be used is implementation-defined, but implementations are recommended to use the latest Unicode version. Identical text appears in the normative references of Functions and Operators. I propose that we add the same text to Appendix A.1 of XSLT 2.0 (Normative References), linking to it from the places cited in this bug report. ("implementations are recommended" is horribly ungrammatical: it's the latest version that is being recommended, not the implementation. I'm very tempted to change it to "implementations are advised". But we can live with the existing text in the interests of bug-compatibility.) 23359 2 mike 2009-01-30 13:05:55 +0000 Erratum E34 has been drafted to add a reference to the Unicode specification, using the same words as in the XPath 2.0 specification. (Note that this is a manual change, because of the technology used to build the bibliography). This bug report is therefore being marked fixed and closed.