| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
I'll trust you on the ttf parsing, but otherwise the patch looks reasonable. |
Sorry, something went wrong.
|
Oops, made a typo with a push and accidentally closed this. |
Sorry, something went wrong.
|
If someone wants to check the code against documentation, composite glyphs are described at https://docs.microsoft.com/en-us/typography/opentype/spec/glyf#composite-glyph-description and 2.14 fixed-point format at https://docs.microsoft.com/en-us/typography/opentype/otspec181/otff#data-types (search for F2DOT14). |
Sorry, something went wrong.
If I run outside the test framework, it appears to be okay? |
Sorry, something went wrong.
Yes, I couldn't reproduce this. It might have been some problem with an intermediate version, as I might have forgotten to compile the extension when running some test. |
Sorry, something went wrong.
To clarify, I can reproduce if running in the test suite, by removing the explicit extension from the comparison settings. This is because tests disable hinting with plt.rcParams['text.hinting'] = 'none'; if you run the script outside the test suite, but add that, then you get the weird streaks. Any setting other than 'force_autohint' or 'auto' (same thing to FreeType, latter is what we call our default) will do it, so it seems to be something wrong in the font hinting itself. |
Sorry, something went wrong.
|
The test failures are because of unrelated Pandas deprecations; apparently Pandas 1.1.0 is now available |
Sorry, something went wrong.
|
This is already fixed on master; you should rebase if you're having trouble with it. |
Sorry, something went wrong.
The GNU Free Serif font has a wide variety of characters with which we can exercise the linear transforms used in TTF composite glyphs.
These could increase the file length in case of fonts with many composite glyphs.
|
It looks like you may have accidentally reverted some things in that last rebase? |
Sorry, something went wrong.
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
You're right, it looks like I lost the suggestions committed via the Github web UI. I committed those again. |
Sorry, something went wrong.
|
See #18181 for an alternate solution, though (which can reasonably avoid adding a new font file in the repo, and in any case seems more robust in the long term, as it can Type3-subset any font that FreeType can outline-decompose). |
Sorry, something went wrong.
Still approving, but perhaps make a decision wrt #18181 first.
|
This branch was also in the main repo; I've now deleted it, as I assume that it's out of sync with this one on your fork that's been rebased. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #17197
I added a test using Free Serif, which has plenty of composite characters such as arrows drawn by rotating other arrows.
PR Summary
PR Checklist