W3C home > Mailing lists > Public > www-style@w3.org > October 2003

CSS21 16.5 Capitalization text-transform

From: Tex Texin <tex@i18nguy.com>
Date: Thu, 16 Oct 2003 05:22:11 -0400
Message-ID: <3F8E6343.710045EE@i18nguy.com>
To: www-style@w3.org
Cc: W3c I18n Group <w3c-i18n-ig@w3.org>

A couple of comments on text-transform-

The first is a pet peeve of mine, which I hope can be addressed.

I find in a number of browsers, that if text-transform is used to change case,
and a user highlights and copies the text to the clipboard (on Windows anyway),
the text that is placed in the clipboard is the original text (ie without case
changes) not the properly cased text displayed in the highlighted region.

I think this behavior is very contrary to user expectations.
It would be good if the CSS spec would specify cut/copy clipboard behavior with
respect to functions that change text.
Should the original text or the resulting text be placed on the clipboard?


Second, the spec says:

"...consider the value of 'text-transform' to be 'none' for characters that are
not from the Latin-1 repertoire and for elements in languages for which the
transformation is different from that specified by the case-conversion tables
of ISO 10646 ([ISO10646]). "


a) I suspect you mean EITHER/OR not AND. 
ie the value can be none if characters are EITHER not from Latin-1 OR for
elements...

For example the letter i uses different conversion values in Turkey, and I
assume that even though it is a latin-1 letter, you intended for the conversion
to not be required.

I guess if the AND is intentional, you are saying that it is better to do no
case conversion than do the wrong conversion.
However, this seems silly, since then implementors need to have a list of
characters that have different conversions for certain languages and insure
that no conversion is performed. At the point you are detecting these
characters and language contexts, you may as well implement the correct
conversion.


b) From an international perspective, I don't see why you mention latin-1 at
all. Why should latin-2 users for example not have the benefit of
text-transform? Why not simply require support for the 10646 case conversion
table, since Unicode character support is more generally required elsewhere?
Given everything else needed to implement CSS, the Unicode case conversion
table seem to be a very small burden to implementers.

3) The reference to 2070 should be upgraded to rfc 3066.
Also, what should occur if the empty language tag is specified for the language
in XML? Use the default conversion or perform no conversion? What if the tag is
"UND"?

tex

-- 
-------------------------------------------------------------
Tex Texin   cell: +1 781 789 1898   mailto:Tex@XenCraft.com
Xen Master                          http://www.i18nGuy.com
                         
XenCraft		            http://www.XenCraft.com
Making e-Business Work Around the World
-------------------------------------------------------------
Received on Thursday, 16 October 2003 05:23:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:24 GMT