- From: Uma Umamaheswaran <umavs@ca.ibm.com>
- Date: Thu, 15 Nov 2007 15:12:18 -0500
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: www-style@w3.org, "'WWW International'" <www-international@w3.org>
If one is going to add any case-insensitivity related material to CSS,
please do not forget the Turkish i problem. One fo the smart editing
tools we had was helping by making all tags to be lowercase or uppercase
etc. respecting the system locale setting. But the results had to be made
non-locale sensitive (or disabled for Turkish users) for such keywords
which are fixed in standards .. so that lowercase i remains dotted and
uppercase I remains un-dotted etc.
Best regards, Uma
V.S. UMAmaheswaran, Ph.D.
Globalization Centre of Competency, IBM Toronto Lab
A2/SZ8, 8200 Warden Avenue, Markham, ON, Canada, L6G1C7; +1 905 413 3474;
Fax:905 413 4682; TieLine 313-3474; email: umavs@ca.ibm.com
fantasai
<fantasai.lists@i
nkedblade.net> To
Sent by: www-style@w3.org, "'WWW
www-international International'"
-request@w3.org <www-international@w3.org>
cc
2007-11-15 13:54 Subject
[CSS21] Case-insensitivity not
defined
Henri Sivonen brings up the point that ASCII case-insensitivity and
Unicode case-insensitivity are not the same and that we should define
what we want for CSS. For example, should WIDTH and WĘDTH match?
WĘDTH and width? Should Greek identifiers match case-insensitively
as well? Accented Latin characters? For that matter should 'e' plus
combining acute accent match eacute?
a-z and A-Z need to correspond, but beyond that the use of other
characters in CSS identifiers is limited to mostly to namespace
prefixes and counter names, neither of which are in widespread use.
~fantasai
Received on Friday, 16 November 2007 14:47:14 UTC