- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Sep 2020 15:14:42 +0000
- To: public-css-archive@w3.org
I agree with @jfkthame. There must be plenty of languages which, labelled properly, would not trigger the shaping required from a font, whereas the OT tag could be used to indicate that "the rules appropriate to <some_other_language> work also for this language". Here's another example. The Scheherazade font has the ability to turn this:  into this, for Kurdish (exactly the same code points):  Kurdish can be labelled using `ku`, but that's actually a macrolanguage in BCP-47 which groups together `ckb` (central kurdish), `kmr` (northern kurdish), and `sdh` (southern kurdish). That transformation will be applied if you label your content as `lang="ckb"` or `lang="kmr"`, but not if it's labelled `lang="sdh"`. Also, if your content is (and it may well be) labelled as `lang=ku`, that transformation will not be applied, either. However, if you use `font-language-override: kur` you _will_ get the transformation, whatever language tag you use. (Note that `kur` is not a BCP-47 language tag, btw.) So, basically, `font-language-override` is not a duplicate selector for language, it's a selector for a particular set of glyph transformations in a font, which happen to be grouped and labelled along linguistic lines (though not necessarily with BCP language tags), which can be applied if the appropriate `lang` attribute for the content doesn't produce the desired effect. hth -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5484#issuecomment-688946215 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 September 2020 15:14:44 UTC