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

Support CMap-data with only strings, when parsing TrueType composite fonts (bug 920426) #14057

Merged
merged 1 commit into from
Oct 1, 2021

Commits on Sep 30, 2021

  1. Support CMap-data with only strings, when parsing TrueType composite …

    …fonts (bug 920426)
    
    In the referenced bug, the embedded fonts contain custom CMap-data that only include strings. Note how for embedded composite TrueType fonts we're using the CMap-data when building the glyph mapping, and currently we end up with a completely empty map because the code expects only CID *numbers*.
    Furthermore, just fixing the glyph mapping alone isn't sufficient to fully address the bug, since we also need to consider this "special" kind of CMap-data when looking up glyph widths.
    Snuffleupagus committed Sep 30, 2021
    Configuration menu
    Copy the full SHA
    d3ca28b View commit details
    Browse the repository at this point in the history