Western Diacritics in Windows Vista

coop's picture

Hi all,

I have an opentype font (OTF) that works fine on the Mac OS platform and Windows XP, but in Windows Vista the Western Diacritics are cut off. Can anyone think of a reason why this might be.


vinceconnare's picture

Generally clipping is caused by an incorrect WinAscent value. The WinAscent and WinDescent are the highest and lowest values in the WinANSI character set (original spec definition).

1. is the font PostScript based outlines output as an .otf file?
2. What application are you using?

I doubt Vista is using a different method of height calculation since the WinDesent and WinAscent and many other metric information goes back to the original bitmap formats in most operating systems and these usually are kept so they don't break existing 'things'.

Reed Reibstein's picture

In what contexts are they "cut off" -- in Microsoft Word, Photoshop, InDesign, Quark, etc.? And does "cut off" mean completely missing or present, but not completely (e.g. half gone)?

EDIT: Obviously Vince has a much better idea of how these things work, so feel free to ignore my questions for his.

coop's picture


How do apply the correct WinAscent value?

Why is this just a problem in Vista ?

Yes it's a OTF font, and it seems to occur in most applications.

vinceconnare's picture

is it your font or someone else's? FontLab can open it and you can view the values in the 'font info'

if it is a TrueType based font you could run it through the Microsoft Font Validator and it will kick up a bunch of errors that probably will relate to the heights in the 'OS/2' table.

If the font is CFF based OTF then it's not going to work in the Validator.

the font is in 1000 units.

p.s. I'm still waiting for my copy of Vista to be sent so don't have it yet or the new Office.

Thomas Phinney's picture

"Most applications" is not very specific or helpful. Please name specific applications it does or does not occur in! We need to know if these are GDI applications, WPF applications, or CoolType applications....

It probably is a usWinAscent problem. Or more accurately, an application problem, as many apps incorrectly use usWinAscent for clipping, in violation of the specifications since day 1. However, since this is a well-known application defect, font makers try to work around it. But without more info, we can't say for sure.



Syndicate content Syndicate content