Opentype font with strange behaviour

Joebob
21.Mar.2008 2.37am
Joebob's picture

Hi,

I recently posted a problem regarding an Opentype font (dearJoe 4) which seemed to be problematic when used in Word. Since then a couple of new problems have arised which are of a different nature and so my previous post’s title doesn’t quite fit the problem anymore. Since the previous post only got one reply I thought it might be a good idea to post this again, with a title that suits the problem better.

So here’s the problems:

“In Word:
The font is listed (in it’s style). When I select the font, the resulting type in the font window and the document says dear Joe 4, but looks like a standard font. It appears that it is not reading the font file, but is automatically substituting another font.

In Photoshop:
The font name does not even appear in the list.

In Corel Draw:
The font name appears in the list and the font works fine.”

And also:

“Testing the TrueType format of the DearJoe Four font in my Win2000 system using Publisher2000 and get an error message saying the font is not available on my system, however, when I selected ’use it anyway’ I was able to continue and use the font without fault.

Using the font in a variety of alternate applications I found the font to function as expected, without fault.

~however~

Testing the font in a WinXP system in Publisher2003 I’m experiencing similar ’not available’ errors, however, I’m not getting the proper font when selecting ’use it anyway’”

So obviously there’s something wrong with the font...
I have generated the font the same way as I always do and this problem has never occured. I just can’t figure out where the problem is. Maybe it’s got something to do with the fact that the font has A LOT of kerning pairs, but please, if someone would be so kind to check this font I’d be happy to send the file to them.

Thanks in advance and best regards,



dberlow
21.Mar.2008 4.57am
dberlow's picture

I don’t know, but are digits allowed in font names?

Cheers!


John Hudson
21.Mar.2008 6.07am
John Hudson's picture

Have you checked your codepage coverage support in the OS/2 table? If you are seeing a different font in Word, that usually indicates that RichEdit thinks the font is unsuitable for the language you are trying to type, which may be due to incorrectly set codepage support in the OS/2 table. That would explain why the font might work okay in some other apps, which might not be performing the same checks as RichEdit.


Joebob
3.Apr.2008 1.31am
Joebob's picture

It seems like the problem was in the fact that there was an extra space at the end of the font’s family name... Now that this space was removed the font works fine.

Thanks for replying and best regards,

Joe


Thomas Phinney
5.Apr.2008 11.18am
Thomas Phinney's picture

I believe that’s one of the many things that the AFDKO tool “CompareFamily” checks for.

You might want to try running your future fonts through this for feedback.

Cheers,

T