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
CFF->TrueType #802
Comments
something like this? |
Yes please! I'm starting to think that we should move Snippets inside Lib/fontTools so they can be called... |
hmm, I wouldn't like to move the Snippets inside the core library. They are by definition incomplete, otherwise we would have already done that. What I'm thinking instead is have a new To avoid a circular dependency between fonttools and cu2qu, I was thinking we could split cu2qu in half: one part ( Let me know what you think. |
See discussion at #802 Derived from: googlefonts/cu2qu#47
I just added the "Snippets/otf2ttf.py", please test, thanks. |
Done in 2a4b3d5 |
I'm not sure if it's that simple — the "fonttools convert" function. Would it convert a TTC into multiple TTFs? Would it convert a TTF+gvar into a set of static TTFs? Would it convert an OTF+SVG into a TTF+sbix? And if not, why not? I don't think it's so trivial anymore too define what exactly "convert" means. Such a converter would be great but I don't think it should be placed inside fontTools. It should be a separate app. The OTF+SVG to TTF+sbix conversion obviously would require an SVG rasterizer, other conversions might require FreeType or other dependencies. |
Anyone wants to put together a snippet that uses cu2qu to convert an OpenType CFF to TrueType flavor?
The text was updated successfully, but these errors were encountered: