- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 29 Mar 2009 11:57:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6746 --- Comment #2 from Nick Levinson <Nick_Levinson@yahoo.com> 2009-03-29 11:57:45 --- I don't want to narrow the use or meaning of the present definitions for case insensitivity. They're fine. Rather, I want to make page authoring easier by including, e.g., the u with the umlaut within the reach of some form of case insensitivity, so that when a user types it into a website form's free-form text field common commands that change case, e.g., Perl's uc() and lc() for CGI (and I assume likewise in other Web-frequenting languages including Java and JavaScript), can handle the case of the u with the umlaut as easily as they can handle the case of the unmarked u and so that sorting can be more intuitive and less often giggly. By adding to HTML a definition for _extended-case-insensitivity_, (1) the existing terminology and definitions can be left as they are and their implementations untouched and (2) user agent designers and others can more readily see that case sensitivity extends beyond nondiacritically-marked letters. That would encourage a spread of intuitivity improving usability for a wider user base around the world. The Unicode standard does seem to address some of this but not all of it and, beyond the listing of code points, it seems to have a smaller readership among Web implementors than do Web language standards. Also relevant is Character Model for the World Wide Web 1.0: Fundamentals (2005), section 3.5, <http://www.w3.org/TR/charmod/> (presumably http://www.w3.org/TR/2005/REC-charmod-20050215/), accessed 3-29-09. Adding the definition does not require that the HTML5 standard articulate many steps. Most of the work in support of authoring and programming can be done by others and later. The idea now is simply to get the point in place. -- Nick -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 29 March 2009 11:57:58 UTC