Font dimensions - generate problem

Nick Cooke's picture

When I generate this typeface as an OpenType PS there are no problems, and it works properly.

The thing that seems peculiar to me is when I scroll across the type to select in InDesign or Illustrator (or whatever), it goes from baseline to baseline from one line to the next.

As it's a script the characters are all different sizes, so the Ascender, Descender, Cap height and x height values are all pretty arbitrary, but the ascender and descender values do add up to 1000. The fonts' UPM size is 1000.

Does anybody have any idea why the type is selected like this?

Have I entered some incorrect values? please see the pics.

Thanks.

Eric_West's picture

Nick,

Sorry I can't help you w/your problem, just wanted to say that it is beautiful!

Nick Cooke's picture

Thanks anyway Eric.

Nick Cooke

dezcom's picture

Why is WinDecent different than TypoDecender and WinAcent different than TypoAcender?

ChrisL

paul d hunt's picture

Why is WinDecent different than TypoDecender and WinAcent different than TypoAcender?

vertical metrics how-to

dezcom's picture

Paul, after reading that linked "clarification" I am now more confused than ever.

ChrisL

Nick Cooke's picture

So am I Chris.

Paul, I'll read that article again to see if I can extract some meaning.

Nick Cooke

paul d hunt's picture

well the problem with this article is that the solution is still out to the jury, but it describes the problem very well.

dezcom's picture

Nick's winAcent/WinDecent equalls 1,100 instead of 1,000. Is that right as a solution for him right now while we wait for the jury?

ChrisL

paul d hunt's picture

from what i understand (someone correct me if i'm wrong)

under the latest thinking, the equation should be this:
TypoAscender + TypoDescender + TypoLineGap = WinAscent + WinDescent = hhea ascender (=WinAscent) + hhea descender (=WinDescent) + hhea line gap (=0(zero))

now hopefully that's clear and correct

under this scheme, nick would want to bump his TypoLineGap to 100 to make all these things equal out. even then i'm not sure this would fix the problem as nick has described it.

dezcom's picture

Thanks Paul. That tidies it up a lot. I hope it gives Nick something to try as well.

Maybe his problem has to do more with his applications than his type? Do any other fonts act like this Nick?

ChrisL

twardoch's picture

Nick,

your values look all-right to me.

A.

Nick Cooke's picture

At last! I was just about to post a reply when Typophile went on vacation.

Thanks Paul and Chris for taking time to try to help, it's good to get advice from a couple of fellow 'bezier wranglers' Ha! Paul, I know you're a Script Meister yourself - love Allyson and Zaner Pro.

I altered the metrics according to Paul's equation, minus the Typo Line gap and line gap, (is it necessary to have a value here?).

Could the problem have something to do with 'Splats' extending above and below the bounding box? Or too many points in these characters?

See Olicana

The type selects differently in different programs – see below:

Illustrator:(the word character is selected)

InDesign:

Text Edit:

Word: (does this program not recognise OT features?)

Nick Cooke

dezcom's picture

The current version of Word recognizes a limited set of opentype features but not contextual alternates. Si can chime in but my understanding is that MS is working on it for a future revision.

ChrisL

twardoch's picture

On Mac, Word 2004 does not support any OpenType Layout features at all. On Windows, Word 2003 it supports "ccmp", "mark" and "mkmk". I believe that Word 2007 also supports "kern".

Regards,
Adam

Syndicate content Syndicate content