![]() ![]() ![]() Alternately, if I can somehow transfer the kerning classes & features of my Glyphs motherfile into the stroked versions I’ll be exporting from FontForge, that would also work. Ideally, I’d like to import those shapes back into Glyphs in order to use the kerning classes and features I had originally defined. I think I’m going to open all paths, then, and produce a bunch of stroked outline versions of the font in FontForge. I’ve already checked, and the open paths expand flawlessly, yielding much nicer results than the pre-expanded outlines I tried earlier. When I open it with FontForge, all paths are closed again (I don’t know whether that’s due to the file or FontForge’s treatment of it), but I can just reopen them manually – tedious, but feasible, especially if I only have to do it once. When I use it in Adobe (looking at illustrator right now) when I hit the space bar, a rectangular cliff pops up between letters. But the font still generates if I keep the em size at 1000. OK, I have managed to export my open-path version of the font with the trick you proposed. I also get 'self intersecting' and 'missing points of extrema' errors. Or wait for a better stroking function to be implemented in Glyphs…? I believe FontForge is Open Source would it be possible to use its Expand Paths algorithm for a Glyphs plugin? I guess I need to stick to the thicker weight, then. I could probably get rounded terminals in Glyphs by applying an additional “Round Corners” filter, but that wouldn’t fix the oogly join on the bottom left of, for instance, gets its outside and inside stroked separately, and using Remove Overlap then does weird things in both FontForge and Glyphs. I’ve tried it out for two characters, and frankly, it looks much less attractive than in FontForge: I suppose I could use the rotation tools in the single-character editing environment, but then I’d have to do that manually for each character, right? (2) I don’t see any rotation functionality in the Transformations dialog or related menus. Also, FontForge doesn’t seem able to read UFO. (1) I tried exporting the unstrokes paths with UFO, but the glyphs came out empty. Is there a macro available for Glyphs that does a better job without destroying all the meta-information in the Glyphs font file? To make things worse, some glyphs just crash FontForge with SegFault during the “Expand Glyphs” procedure, which forced me to redo the same few steps several times until I eventually gave up. It’s a horrible workflow, though, especially since all the live references and kerning classes are lost. Now, I’d like to make use of a path stroking tool to do most of the work… but the built-in “Offset Paths” function of Glyphs is extremely limited (e.g., no diagonal stress or rounded caps) and produces uneven stroke thickness.Īs a fallback solution, I’ve tried expanding the path to 1 unit thickness in Glyphs, exporting to OTF, importing into FontForge, using “Expand Strokes” there, and then re-import the shapes into Glyphs via the OTF format again. I designed it as a collection of zero-width paths that look very pretty in the editor, but of course I have to convert them into outlines for actual use. I’ve been working on a font that should look a bit like it’s written with a ballpoint pen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |