-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
test for seac-like endchar command #77
Comments
Can you prepare a test font with just one or two glyphs? I'll then add a test case to the test suite. |
https://github.com/harfbuzz/harfbuzz/blob/main/test/api/fonts/cff1_seac.otf |
Nice, that was fast! The harfbuzz test fonts are licensed under SIL Open Font License V1.1, so you can use them for the test suite. |
The font is a derivative of Adobe Source Sans Pro, equally under OFL-1.1 license. Taken from the HarfBuzz test suite, but using a different font name to comply with the OFL licensing terms. #77
The font is a derivative of Adobe Source Sans Pro, equally under OFL-1.1 license. Taken from the HarfBuzz test suite, but using a different font name to comply with the OFL licensing terms. #77
Not updating test reports for the native rendering stacks because our C++ codebase cannot be compiled anymore with current clang (15.0.0). This is a separate issue, independent of testing CFF fonts. Fixes #77 Related: * foliojs/fontkit#322 * opentypejs/opentype.js#117
Not updating test reports for the native rendering stacks because our C++ codebase cannot be compiled anymore with current clang (15.0.0). This is a separate issue, independent of testing CFF fonts. Fixes #77 Related: * foliojs/fontkit#322 * opentypejs/opentype.js#117
I just fixed a bug in opentype.js that could make for a new test case, see opentypejs/opentype.js#633
The CFF
endchar
command supports a compatibility to the Type 1seac
command in order to implement standard encoding accented characters. This seems to also affect fontkit and it would help to be caught for other parsers/renderers as well.The text was updated successfully, but these errors were encountered: