These comments have been endorsed by the I18N Core WG.
"A language and/or country specifier in conformance with [RFC3066]": Please refer also to the successor of RFC 3066, i.e. please write "A language and/or country specifier in conformance with [RFC3066] or its successor".
Do you support names in the sense of xml 1.1?
Have you thought about formatting of ruby?
It would be good to have links to the various sections in the indirectly-derived traits overview (end of sec. 4.1)
The links to targets in this list (e.g. this link) don't work.
longdescriptions are encoded in iso-8859-1, e.g. this longdescription, whereas the main document is encoded in utf-8
The Language Property: Please refer to RFC3066 or its successor for the construction of language codes.
|8||Editorial||ISO639-3 is in the reference section, but not in the main text.||-||-|
|9||Editorial||Linebreak of code in examples does not work sometimes, see e.g. the example "This example shows a very simple page layout specification. ".||-||-|
|10||Sec. 5.11||Property Datatypes, the datatypes for name and character: please refer to the productions of xml 1.1 instead of xml 1.0.||-||-|
|11||Sec. 5.11||On the datatypes country, language and script: The revision of RFC 3066 solves some problems which arise with the the underlying ISO standards (e.g. reliability of values, matching of values). You might have a look into this.||-||-|
|12||Sec. 5.11||uri-specification: please refer to rfc 3987 (IRI) instead of 2396, and add a normative reference to rfc 3987.||-||-|
|13||Sec. 7.10.1||"country": you refer to RFC3066; in other sections, you refer to the ISO country codes. Please be more coherent. We would propose a solution like in the comment ||-||-|
|14||Sec. 7.10||"hypenation properties": these properties are also sensitive to RFC3066, so please think about a solution like .||-||-|
|15||Reference to Unicode||Please change the reference to the Unicode standard as described in the
character model (fundamentals), e.g.
Unicode The Unicode Consortium, The Unicode Standard, Version 4.1.0, ISBN 0-321-18578-1, 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).
|16||Sec. 7.2.6||why don't you refer to the definitions of xslt 2.0 for number to string conversions?||-||-|
|17||Sec. 7.26 and in other parts of the spec||"In the XML markup of the figure above, the characters are represented by their presentation form (and not their Unicode code points). The order in which the characters are depicted is their storage order. " You might introduce the terminology "logical order" (which you named storage order) and "visual display", see also character model (fundamentals) on this topic.||-||-|
|18||Sec. 7.29.7||"This version of the writing-mode property covers the base writing-modes that are used as the official languages of the United Nations." Should this be "This version of the writing-mode property covers the base writing-modes that are used *for* the official languages of the United Nations."?||-||-|
|19||Sec. 7.30||xml:lang: For this comment, see also comment .||-||-|
Version: $Id: xsl1.1-review.html,v 1.2 2005/10/02 03:21:42 fsasaki Exp $