- From: <bugzilla@jessica.w3.org>
- Date: Sat, 09 Mar 2013 11:05:44 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17859 --- Comment #14 from mark@macchiato.com --- > Well we can't use lang="" itself, since that would break existing pages I'm not really up on this topic, and am trying to understand the issue. Is it that if you had <input type="date" name="fname"> and there was an enclosing tag with lang="de-AT", that only dates appropriate for de-AT would be accepted? BTW, I was looking at instances of 'locale' in http://www.w3.org/html/wg/drafts/html/master/single-page.html#language, and happened to run across the table: Locale language Suggested default encoding ar UTF-8 be ISO-8859-5 bg windows-1251 ... This guidance may be somewhat out of date. I looked at stats for our search indices for a few TLDs, and UTF-8 has risen significantly. For example, for .jp, .th, and .de it is significantly greater than all other encodings combined. For bg, mentioned above, it is about 2x all other encodings combined. Only for .cn is it about the just less than another encoding, and for .ru just above another encoding. This would take a bit more work, and should be confirmed by some other search engines, but that table might need a bit of tweaking. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Saturday, 9 March 2013 11:05:49 UTC