-
Notifications
You must be signed in to change notification settings - Fork 499
GPOS lookupType 9 support #491
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
base: master
Are you sure you want to change the base?
GPOS lookupType 9 support #491
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase on the latest code and make requested changes, otherwise this looks good.
@@ -36,6 +36,8 @@ Position.prototype.getKerningValue = function(kerningLookups, leftIndex, rightIn | |||
const subtables = kerningLookups[i].subtables; | |||
for (let j = 0; j < subtables.length; j++) { | |||
const subtable = subtables[j]; | |||
// Subtables not supported come with an error | |||
if (subtable.error) continue; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe make it log the error when it comes across one?
Pinging @AlexandreRivet |
This will be covered by #557 |
a83fe80
to
995ec63
Compare
I was about to close this but tested it before just in case, and with this PR |
Description
Add support for GPOS lookupType 9 to be able to manage other extended lookupType. 🤩
Motivation and Context
I noticed, by using this font WorkSans, I was not able to get kerning values. Diving into this problem, I found it was because GPOS lookupType 9 was not supported and only lookupType 2 was used in getKerningTables.
How Has This Been Tested?
Types of changes
Checklist:
npm run test
and all tests passed green (including code styling checks).