Re: [clreq] Consider using ITS "Locale Filter" instead of data-lang

we don't actually need step 1, so it comes down to replacing all 
occurences of data-lang with its-locale-filter-list, which is an ITS 
defined name.  

the downside is that it takes 2.5 times as long to type the attribute 
name for a content author, and since these attributes come in pairs, 
that's 5x the typing for each chunk of data labelled. Plus it makes 
the code marginally harder to read. In reality, ITS only defines data 
categories, and the actual names of attributes in the implementation 
doesn't have to use the same names (so eg. in HTML we use the 
translate attribute rather than the its-translate attribute). That's 
less of a problem if we are copy-pasting.

but i guess it makes sense to use the same attribute name as in the 
ITS standard. One advantage being that it is clearer to people why 
this attribute is not the same as using the lang attribute, another is
 that it shows that we are using ITS concepts. (Note also that 
its-locale-filter-list validates.)

i guess we could try it, and if it's too long we could revert back to 
data-lang, or even data-locale.


-- 
GitHub Notif of comment by r12a
See https://github.com/w3c/clreq/issues/76#issuecomment-123260405

Received on Tuesday, 21 July 2015 10:46:58 UTC