From: <scr...@at...> - 2017-04-06 11:56:23
|
A good start would be to find a book or books on calligraphy and/or designing type. Because of the way our eyes work, if you make a curved edge, the bottom of the O, let's say, just touch the baseline, it will look raised above it. To make it look as though it's resting on the baseline, it actually has to go a bit below it. How much "a bit" is, is a function of artistic judgement. Similarly, to make characters look evenly spaced, two Os must be very close together compared to two Ns or Hs. Get some books on calligraphy and type design. They'll repay study because you'll be able to avoid making all the puzzling, difficult-to-understand mistakes that people with no background make. On Wed, 5 Apr 2017 18:14:43 -0700 (MST), you wrote: >I'm new to this font racket and I have a beginner question. How should I >design the glyphs with respect to the borders and guides and stuff? My >intent is to have everything touch (but not cross) the baseline. I would >have the tallest glyph reach the ascent. Is there any reason why I wouldn't >want the left and right borders to hug all glyphs? >The set has the following properties: >A fictional runic font >Only one case (thus above the baseline) >Don't really know what else to say about it. >Any other advice anyone has for a noob would be appreciated. So far I've >figured out how to import a background, do an autotrace and then >painstakingly remove 90% of the control points. I'm sure someone can give me >a tip about how to speed that up. I'm also wondering if there's any reason >for me to use an encoding other than the basic TrueType. |