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.

Sign up for GitHub

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

Jump to bottom

CFF: use latin1 so we can roundtrip non-ASCII in {Full,Font,Family}Name #3202

Merged
merged 1 commit into from
Jul 10, 2023
Merged

CFF: use latin1 so we can roundtrip non-ASCII in {Full,Font,Family}Name #3202

merged 1 commit into from
Jul 10, 2023

Commits on Jul 10, 2023

  1. CFF: use latin1 so we can roundtrip non-ascii in FullName|FontName|Fa… 

    …milyName

Fixes #2898

use Latin1Converter for all name strings, and not just for Notice and Copyright. Then at least we can round-trip binary=>TTF=>binary, even if the TTX will not show the intended string.

Given that any non-ASCII in FullName can be considered broken, this at least this would let us round-trip without error.
    @anthrotype
    anthrotype committed Jul 10, 2023
    Configuration menu
    Copy the full SHA
    a8bd0ef View commit details
    Browse the repository at this point in the history