Re: [csswg-drafts] [css-text] Clarify what ligatures are optional

I'm actually trying to fix the issue in blink mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=1458053#c4 and https://bugs.chromium.org/p/chromium/issues/detail?id=896033 . In doing so I came across the even simpler issue of letter-spacing only affecting 'liga' and 'clig' and apparently not other sorts of ligatures (and it seems it should). Basically, should letter-spacing also affect 'dlig' and 'hlig' and possibly others. I'm mostly looking for clarification on this somewhat simpler question (and quite literally the title of this issue). So maybe that is a 0th issue.

I have actually (for other reasons) asked about having harfbuzz let the user know if a glyph clusters should not be broken at all (see https://bugs.chromium.org/p/chromium/issues/detail?id=895594 ) due to being formed from required features. It seems like that may help with issue 1. However, that wouldn't have helped in this specific case since the glyph clusters aren't actually marked as required by the shaper/font/script. I imagine one should never split up grapheme clusters (the codepoint level clusters).

I'm also making inquires into Noto Khmer and its use of 'clig' here for what appear to be required substitutions (the latest publicly available version has the same issue) . Note that it may just be a bug in HarfBuzz that 'clig' isn't a required feature in 'khmr' script, since https://docs.microsoft.com/en-us/typography/script-development/khmer#features marks it as required. It appears that HarfBuzz currently treats 'clig' in this situation as 'default on' but not required, I've opened https://github.com/harfbuzz/harfbuzz/issues/1310 to ask about that.

-- 
GitHub Notification of comment by bungeman
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2644#issuecomment-432774658 using your GitHub account

Received on Wednesday, 24 October 2018 18:26:58 UTC