Comment 6 for bug 716676
Revision history for this message
| Windell Oskay (windell) wrote Re: No support for stroke-based ("engraving") fonts | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
@Pablo Trabajos @~suv:
We have been using those "featurecam" fonts for some time, and hand-editing them. Some things to note about that.
1.) Licensing for the featurecam "Machine Tool" fonts is not clear. They are available for free-as-in-beer download, but we have been hesitant to recommend their use because that availability could be retracted at any time. This is not necessarily an issue, as there may be other sources that could be freely licensed, and we could (in principle) always compose new TTF fonts using the Hershey glyphs.
2.) Inkscape does automatically close the path of poorly formed TTF fonts. This is the feature of Inkscape that prevents true compatibility with TTF-based engraving fonts. I believe that this is a feature, not a bug, of Inkscape. In other words, I believe that this is the correct behavior in the vast majority of cases. However, if there were a way to add core support for engraving fonts that did not cause other conflicts, that *would* be a better solution.
3.) One of our Eggbot team members (Dan Newman) wrote the "Machine Tool Fixup" extension as a very specific fix to the path-closing. It works in most cases. In light of the new extension and (1) above, we had been planning to withdraw "Machine Tool Fixup" and no longer recommend the use of those specific fonts.