- From: Felix Sasaki via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Jul 2015 10:00:52 +0000
- To: public-i18n-archive@w3.org
fsasaki has just created a new issue for https://github.com/w3c/clreq: == Consider using ITS "Locale Filter" instead of data-lang == Looking at the data-lang attribute the functionality seems identical to ITS "Locale Filter" http://www.w3.org/TR/its20/#LocaleFilter One should consider replacing data-lang with the standardized "Locale Filter" mechanism. This would be relatively easy: 1) at the top of https://github.com/w3c/clreq/blob/gh-pages/index.html add its-locale-filter-list="*" its-locale-filter-type="exclude" 2) replace all data-lang attributes with an its-locale-filter-list attribute. Its value is the same like for data-lang 3) replace in https://github.com/w3c/clreq/blob/gh-pages/script.js and in the CSS selectors all selectors for data-lang with a selector for its-locale-filter-list Note that locale-filter is also understood by the w3c validator, so your document will keep to be valid, see this example https://validator.w3.org/nu/?doc=http%3A%2F%2Fwww.w3.org%2FTR%2Fits20%2Fexamples%2Fhtml5%2FEX-locale-filter-local-html5-1.html See https://github.com/w3c/clreq/issues/76
Received on Tuesday, 21 July 2015 10:00:53 UTC