Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prohibition in GSUB Multiple Substitution Lookup contradicts long-standing practice. #879

Open
drj11 opened this issue Dec 6, 2021 · 2 comments
Assignees

Comments

@drj11
Copy link

drj11 commented Dec 6, 2021

GSUB section 2.1 Multiple Subsitution says the following:

The use of multiple substitution for deletion of an input glyph is prohibited. The glyphCount value must always be greater than 0.

(The previous version of the OpenType specification says this too, it isn't new)

But a 0-length replacement sequence is exactly how the AFDKO Feature File compilation tool makeotf implements the rule to remove a glyph from the input: sub X by NULL compiles a Multiple Substition lookup with a 0-length replacement sequence (and i assume it always has done).

I therefore suggest that years of standing practice bless this implementation detail, and that the OpenType specification is changed. To something like:

Multiple substitution can be used to implement the deletion of an input glyph. When the glyphCount is 0 the input glyph is replaced with an empty sequence, effectively deleting it.

I have raised this point in the AFDKO repo too adobe-type-tools/afdko#1438


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@simoncozens
Copy link

Duplicate of #707 and #673.

@drj11
Copy link
Author

drj11 commented Dec 6, 2021

ahahahahahaaha

@PeterCon PeterCon self-assigned this Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants