My guess is that you have a code-page or Unicode range bit set, eg Arabic, Hebrew or Thai, and you don't have any characters from that range in the font.

Cheers, Si

Hi Si,

Yes, thanks. It was the Greek codepage what was the problem. There are no Greek glyphs in the fonts.
Thanks!

Pieter

When you have a fonts that contain Latin 2, Turkish and/or Baltic, it is recommended that you set the Greek codepage for MS Word.
I think it has to do with the PFM default character.
In Adobe Caslon Pro and Garamond Pro the Greek codepage is set, and the PFM default character is "space". Font names look good in Word. In Tekton Pro the PFM Default character is "bullet",and not "space", and this is what you get

Hi Micha,

Thanks for you answer.

Pieter

When you have a fonts that contain Latin 2, Turkish and/or Baltic, it is recommended that you set the Greek codepage for MS Word.

Why would that be recommended?

Please look at fonts from Adobe and Linotype, containing Latin 2, Turkish and Baltic, but not Greek and/or Cyrillic. These fonts all have Greek flagged. As far as I can remember this had something to do with Word not recognizing the extra Latin characters. Couldn't find were the info is, so it might also have to do with another program.

Thanks. Indeed I found the Greek codepage bit in some fonts, for example Adobe Caslon Pro. Hm. I had never heard of this before.

Is it possible that certain programs will place a font with extended Latin at the very bottom of the font menu (despite alphabetical order) and by setting the Greek, it will place the font back within the main/top font menu?

I've not heard of any Word specific reason to include such a hack in OTF fonts. Perhaps the hack is there to support other applications?

I started writing an explanation of this, but it got so long I made it into a blog post instead.

http://www.thomasphinney.com/2009/02/greek
Should be live within a minute or two.

Cheers,

T

Thanks all, you are a great help!

Pieter