- From: Felix Sasaki via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jul 2015 09:08:10 +0000
- To: public-i18n-archive@w3.org
Strange - I understood during our 1:1 call this week that you would
move forward with its-locale-filter-list.
Keeping data-lang would be a pitty in terms of "dog fooding". We
develop ITS2, reviewed by the i18n group, with no complains about
attribute length. And then it comes to adoption the length concerns
come up?
About "we can certainly say, however, that data-lang represents a
local instantiation of the locale filter data category.": this does
not help if you don't have a mapping between data-lang and the
its-locale-filter-list. You can achieve that mapping via a rules files
in the HTML "head" element:
<script type=application/its+xml>
<its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"
its:version="2.0">
<its:localeFilterRule selector="//@[@data-lang='zh']"
localeFilterList="zh"/>
<its:localeFilterRule selector="//@[@data-lang='en']"
localeFilterList="en"/>
</its:rules>
</script>
This solution is not preferred because people will continue to use
proprietary attributes.
--
GitHub Notif of comment by fsasaki
See https://github.com/w3c/clreq/issues/76#issuecomment-124450476
Received on Friday, 24 July 2015 09:08:12 UTC