- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jul 2020 08:30:21 +0000
- To: public-css-archive@w3.org
> > This is what rlig vs the various other ligature features are supposed to distinguish. > > That should be true, but the boundary is fuzzy even in the OpenType spec: Khmer, for instance, [requires the "clig" (contextual ligatures) feature](https://docs.microsoft.com/en-us/typography/script-development/khmer) for layout, despite it being theoretically discretionary. There's that; and then there's also the fact that ligation (mapping two or more encoded text units to a single rendered glyph) can happen in other OpenType features, depending on details of font construction -- for example, various Indic shaping features may be implemented as ligatures. Ligature lookups are not limited to occurring in features *called* "ligatures". -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5251#issuecomment-654688789 using your GitHub account
Received on Tuesday, 7 July 2020 08:30:23 UTC