AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Using fontlab with mac12/28/2023 ![]() Thomas, please consider making the kerning interface fully controllable by key shortcuts so we can use game pads as it can be currently done in MetricsMachine. But UFO is as much an equal player as we can make it. So, there are perfectly good reasons why FontLab has other format options for saving. Because each glyph is a separate file, there can be some performance issues, particularly when reading or writing fonts with large numbers of glyphs. Whether that data is important to you is another matter. If you pass it through other tools, in some cases data may be lost. UFO requires that some FontLab-specific data is relegated to private places. ![]() However, it will remain to be seen if other tools choose to adopt XFO support. So it keeps all the FL data and there are performance advantages over naked/old UFO because of the reduction in file I/O. XFO is essentially a FontLab-extended UFO packaged in a Zip container. VFC is a FontLab native binary format, and will be faster than anything else for file operations. I still use FontLab 5 so I have to work with VFB otherwise it's purely UFO. Is there any benefit to saving in VFC or XFO? It seems with all the UFO-based apps that UFO would be the most desired. I'm still looking forward for the final release! I'm sure a V/VI symbiosis could work as well I love optimising my beziers (hence I actually finalise illustrations in font software due to Illustrators imprecision) I know where the limits lie, however, if there are ways around this problem (and I'm just configuring my programs incorrect), I'm open to suggestions! I must add though, I'm an illustrator, less of a technician. I guess this has some to do with all the implemented curve aids? (even though turning everything off doesn't give FL5 levels of performance) I've been working around FL5's dated UI and bezier-handling quirks through turning to glyphs for simpler projects, but I'd still like to streamline my workflow and bundle it all together. If you have to draw/adjust thousands of points daily a latency of some milliseconds quickly becomes a strain on your work. The reason I've been sticking with Fontlab V is that Robofont/Glyphs just haven't been able to deliver at the same standard of performance. Anything around 1k-2k points (and editing glyphs with those counts) becomes quite a strain. ![]() Currently even my 'lower' creations are chugging my system down to unusable levels for a decent workflow. However, I really hope the performance for high point glyphs will improve. I've been looking forward to this release, and it looks quite impressive!
0 Comments
Read More
Leave a Reply. |