-
Notifications
You must be signed in to change notification settings - Fork 848
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
gerber: convert font glyphs directly #1568
Comments
From irasc...@gmail.com on July 14, 2011 22:49:57 in general, the more svg elements we can convert directly, rather than going through raster conversion, the better |
From irasc...@gmail.com on July 14, 2011 22:50:53 or sticking with rasterizing, would it be possible to do just the fonts at a higher res? |
From irasc...@gmail.com on July 16, 2011 14:37:52 an technique called distance-mapping might work as a fast way to convert a given svg vector to a raster: http://labs.qt.nokia.com/2011/07/15/text-rendering-in-the-qml-scene-graph/ |
From irasc...@gmail.com on July 19, 2011 15:51:35 QPainterPath has an addText function which takes a QFont. The resulting path is composed of moveTo, lineTo, curveTo. One would have to approximate the curves (both cubic and quadratic bezier) with circular arcs. There is a paper about the cubic bezier approximation at http://itc.ktu.lt/itc354/Riskus354.pdf , also see http://www.cosy.sbg.ac.at/~helmut/Teaching/SEDissertanten/program.pdf , and http://cgcad.thss.tsinghua.edu.cn/~yongjh/papers/cad2000v32n4p253.pdf |
From irasc...@gmail.com on July 20, 2011 03:22:49 QPainterPath also has a number of path-to-polygon conversion functions, so depending on how closely these curves are converted, it might be possible to use these directly. This could also be the means for converting elliptical arcs--because QPainterPath's arcTo is elliptical. |
A while ago I made some progress on this. |
From irasc...@gmail.com on July 14, 2011 05:26:41
Instead of rasterizing fonts, figure out how to convert the font glyphs directly, or somehow attach to Qt's font engine...
Original issue: http://code.google.com/p/fritzing/issues/detail?id=1568
The text was updated successfully, but these errors were encountered: