Add extracted otf glyphs to test data #478
Assignees
Comments
dfrg
added a commit
that referenced
this issue
Jun 7, 2023
Adds support for charstring evaluation. Results are passed to an impl of the `CommandSink` trait that provides hooks for processing both path commands and hinting data. This doesn't do scaling or hinting, but both can be built on top of the sink trait. Removes the existing "low level" parsing code for now because that did not properly handle the hint/counter masks args in the data stream that depend on tracking the stem hint count (and thus, also recursing into subroutines which can apply stem hints). I'll think about how to properly address this. Testing is very light. We need a bit more infra for building a full PostScript "font" object from the CFF/CFF2 tables to support more sophisticated evaluation. Opened #478 to track testing.
|
Also add unit tests for each charstring operator! |
dfrg
added a commit
that referenced
this issue
Jun 13, 2023
Adds support for charstring evaluation. Results are passed to an impl of the `CommandSink` trait that provides hooks for processing both path commands and hinting data. This doesn't do scaling or hinting, but both can be built on top of the sink trait. Removes the existing "low level" parsing code for now because that did not properly handle the hint/counter masks args in the data stream that depend on tracking the stem hint count (and thus, also recursing into subroutines which can apply stem hints). I'll think about how to properly address this. Testing is very light. We need a bit more infra for building a full PostScript "font" object from the CFF/CFF2 tables to support more sophisticated evaluation. Opened #478 to track testing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Make sure
extract_glyphs.pyexports the correct data for CFF fonts, add the constants to font-test-data and use them to actually test charstring evaluation.The text was updated successfully, but these errors were encountered: