It is that time of the font design where I remove overlaps and components.
In the past, I always did the removal, then generated a font and carefully closed the .vlb without saving. Even though it is finished, I may want to come back at some point. Would it be possible to generate a font, then open the font to remove the overlaps etc. and then resave from Fontlab? Would this cause problems?
0
Comments
The other option you propose wouldn't be a problem, but it's just more manual intervention. If that way works better for you, I'd just make a copy of the original and give it an obvious name (e.g., "...-ERASE_ME.vlb") and once you've done all the final production steps on that and generated the fonts, delete it. It's a lot of extra steps that I'd probably mess up on, but do what works for you!
1. delete all component-only glyphs (I mark them all with a specific colour, for safety)
2. select all glyphs
3. Merge contours
and you’re done.
4. Generate font
You mean decompose, right? Not 'delete'.
1. delete all component-only glyphs (this will delete only the component glyph itself, all incidents of the comp. will change to contour this way)
2. select all glyphs
3. Decompose
4. Merge contours.
This is the way I do it.
Ah. I didn't understand what you meant by 'component-only glyphs'. You mean glyphs that only exist in order to be used as components in composite glyphs. I call these ingredient glyphs, and usually prefix their names with 'xx' in order to make them easy to search for and filter.
because you might need do remove overlaps. And for CFF it doesn’t make a difference. For TrueType it would be bad (to remove all).
I use x-100,y-100 scale for these and decompose before final export.
That can happen when you have two copies of a path overlaying each other.
Sure enough, that was it! Thanks.