--- Begin Message ---
|
Subject: |
[OpenType] Re: Question about OS/2.winAscent |
|
Date: |
Mon, 10 May 2004 09:33:32 -0700 |
OpenType list address: address@hidden
You are right. I guess I have never read this carefully enough
before. The last statement is certainly true. The Adobe FDK for
OpenType avoids clipping by setting usWinAscent to the maximum yMax
of any glyph in the font, not just of the ANSI set.
OpenType list address: address@hidden
In http://partners.adobe.com/asn/tech/type/opentype/os2.jsp#wa
WinAscent:
... is distinct from Apple's Ascender value
... usWinAscent is computed as the yMax for all characters in the
Windows ANSI character set.
... Windows will clip the bitmap of any portion of a glyph that
appears above this value.
At first glance these last two statements appear to be incompatible. If
I follow this standard then any characters which exceed the bounding box
of Windows ANSI will be clipped.
What is the appropriate definition of this field?
Subscribe: address@hidden
Unsubscribe: address@hidden
Set list to inactive: address@hidden
Set list to active: address@hidden
Message mode: address@hidden
Digest mode: address@hidden
--
-----------------------------------------------------------------------------------------
Read K. Roberts address@hidden
Adobe Systems San Jose TW12 (408)-536-4402 on Weds
San Francisco (415) 642-5642 Mon, Tues, Thurs, Fri
Subscribe: address@hidden
Unsubscribe: address@hidden
Set list to inactive: address@hidden
Set list to active: address@hidden
Message mode: address@hidden
Digest mode: address@hidden
--- End Message ---