At 7:18 AM +0100 10/3/02, Andrew Dunbar wrote:
>Windows doesn't
>seem to have such a concept though with i18n fonts,
>Uniscribe does actually do some similar tricks. I
>have no idea what OS X does.
There is certainly nothing in the low level font management
and text rendering code on either Windows or Mac OS X that does this
type of thing - by the time you get to rendering glyphs on the
screen, it's just grabbing stuff from a font.
However, as you note, higher level text layout facilities
(Uniscribe & ATSUI, respectively) include the ability to take Unicode
data in conjunction with a font and if specific glyphs are missing,
then fall back to alternatives that might include it, all the way
back to a "last resort" font.
Adobe applications also have a similar concept that their
text engine uses, but which also includes the ability to do "font
metric matching" and Multiple Master font "fauxing".
>Panose information in fonts may also play a part?
There is a HUGE amount of debate in the font/text community
about the idea of "font matching" - which is one reason such things
are being left out of standards like SVG and PDF/X-2.
LDR
--
---------------------------------------------------------------------------
Leonard Rosenthol <mailto:[EMAIL PROTECTED]>
<http://www.lazerware.com>
