FontLab Forum
2012-05-16, 12:25:25 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: FLS5 Mac - TypoAscender/Descender issues  (Read 3547 times)
ArchivePoster
Guest
« on: 2008-01-15, 16:22:00 »

Posted by: Packyman
         
hey all,

i've read the message on the home page about this problem when generating an OTF, and it's really confusing to me. i just got the 5.0.4 upgrade and i'm not used to the changes yet, so maybe i'm missing something. but i keep getting the same warning message:

>>[WARNING] The feature file OS/2 overrides TypoAscender and TypoDescender do not sum to the font bbox size!<<

is there a quick fix for this? the font i generated views and prints fine from InDesign CS3 but i'm worried the warning i'm getting will cause problems for this font later on. i tried all sorts of things yesterday but nothing worked. ANY and ALL help will be GREATLY appreciated! thanks!

-patrick
         
Logged
ArchivePoster
Guest
« Reply #1 on: 2008-01-15, 21:58:00 »

Posted by: Rmullin3
         
oh boy if this question gets answered it was worth all the trouble of becoming a msn member.
 
this seems to happen when you use auto-calculate in the "truetype specific metrics" window in "font info"
 
when this happens to me i usually swear a lot. a good idea is to save before messing with the font info. the fix, ive found, is to copy each glyph into a new font. although thinking about it, you could restore the defualt values into the page by opening a new font file and copying those values.

         
Logged
ArchivePoster
Guest
« Reply #2 on: 2008-01-16, 19:10:00 »

Posted by: rroberts
         
This is just a warning, not an error.  If  the line-spacing for your font looks fine in MS Word and InDesign, and tall letters aren't getting clipped, you are fine.

The problem has nothing to do with the font bounding box size. The wording of this error is misleading, and is a bug in the software library used by FontLab to generate OTF fonts. This is supplied by the Adobe Type Dept, and I will fix it on the next release of the Adobe FDK.  The issue is that the TypeAscender and TypoDescender do not sum to the em-square.

It is preferred practice of the Adobe Type Dept to set the LineGap to 200, the TypoAscender to what it should be for the font, and the TypoDescender to whatever it needs to be to make the TypoAscender + TypoDescender == em-square size. However, this rule is not followed if it doesn't fit the font, and it need not be a rule that you ever follow. Just remember what the values are for.

TypoAscender is used by layout apps to determine the distance from the top of the text frame to the first text base-line.

TypeDescender is used to determine the distance from the last text base-line to the bottom of the text frame.

The sum of these and LineGap sets the line-spacing, the distance between the base line of one text frame and the next.

This is all the ideal, pre the OpenType spec, and is not followed by anything other than high-end layout apps, but in the long run we all hope that regular programs will get smarter about layout.

You should read the discussion of the several sets of vertical metrics and the compromises involved, written by John Hudson at:
http://typophile.com/node/13081?
         
Logged
ArchivePoster
Guest
« Reply #3 on: 2008-01-16, 20:30:00 »

Posted by: Packyman
         
thanks for the feedback! i DID read the article by john hudson but i'm still struggling. i sent in a request to fontlab, so hopefully they'll respond.
         
Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!