- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 30 Mar 2009 05:11:11 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6746 --- Comment #7 from Nick Levinson <Nick_Levinson@yahoo.com> 2009-03-30 05:11:10 --- We can define what we mean. When anyone else has different needs, we can still pursue ours and solve them. If the Unicode organization or any other will have to catch up to a definition that is superior for our purpose, so be it. When theirs are superior, we'll use those. HTML can handle many languages. An element can declare the pertinent language for a page. Units less than a page can have their own languages declared, so that a page can be in English and a passage within it can be in Turkish and browsers will recognize that because of the tagging. That's already provided for within HTML. The example you give would be a violation of the definition already in HTML5, because the case insensitivity accommodation must be within the range of code points that is within ASCII, and I proposed that we add a term and a definition that encompasses non-ASCII, the need for which your example supports very well. My proposal doesn't depend on every letter having exactly one capital form and exactly one lower-case form. It depends on enough letters having one or more of each case and perhaps of other cases, if any, to justify recognizing that case matters beyond ASCII. As with many other aspects of life reflected in Internet standards and in de facto standards for OSes and firmware, we can create a framework that leaves room for exceptions and is still tightly enough controlling and we can identify the exceptional cases requiring exceptional treatment. The proposal allowed deferring compiling lists until later and allowed for others to do any compiling. The Wikipedia article suggests that just that strategy (framework and exceptions) has been employed elsewhere for the Turkish issue, e.g., by an application designer. I think we can do the same for HTML, we should given that HTML is more important and more shared than any single app that might run on HTML, and we largely already have. The case you give shows the need for the additional definition I proposed or for something along that line. Thank you. -- 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 Monday, 30 March 2009 05:11:21 UTC