Re: [CSS21]text-transform, reference to 10646 for case-conversion wrong

On Saturday, February 1, 2003, 2:43:31 AM, Michel wrote:


MS> The following text:
MS> <<
MS> Conforming user agents may consider the value of 'text-transform' to be
MS> 'none' for characters that are not from the Latin-1 repertoire and for
MS> elements in languages for which the transformation is different from
MS> that specified by the case-conversion tables of ISO 10646 ([ISO10646]). 
>>>

MS> The reference to 10646 doesn't make sense. ISO 10646 does not have case
MS> mapping tables. I guess I should know, I am [also] the project editor of
MS> that one :) You should reference Unicode instead. CSS3 text already
MS> references Unicode for that.

I think this was due to a late (and inadvisable) change of 'Unicode"
to 'ISO 10646' throughout the CSS2 document in response to some
comment or other.

Which makes no particular sense for the places where they are
equivalent (character repertoire) and is completely wrong for areas
where Unicode provides per-character data beyond 10646.

Like Michel, I would support changing 10646 to Unicode throughout,
with an explanatory not in the refs section briefly describing that
10646 and Unicode are aligned.

The get-out clause for that funky non-Basic-Latin wierdo international
text ;0) while perhaps understandable in 1997-1998 also looks quaint
and antiquated in 2003 and should be removed in CSS2.1; its just
another undesirable difference between "HTML" and "XHTML or generic
XML" CSS renderers.

Instead, just say that the text-transform does what the Unicode case
conversion tasbles say and thats it. Simple, reliable, interoperable.


-- 
 Chris                            mailto:chris@w3.org

Received on Monday, 3 February 2003 12:19:02 UTC