RE: Windows Glyph Handling

From: Peter Constable (petercon@microsoft.com)
Date: Thu Aug 25 2005 - 08:19:12 CDT

  • Next message: Michael \(michka\) Kaplan: "Re: Windows Glyph Handling"

    > From: unicode-bounce@unicode.org [mailto:unicode-bounce@unicode.org]
    On
    > Behalf Of Philippe Verdy

    > Note that a standard does not mean that it will not be proprietary as
    well

    An ISO standard allows for proprietary IP made available under
    reasonable and non-discriminatory (RAND) licensing terms.

    > The problem is that Uniscribe is not replaceable
    > by
    > a Open-Type compatible layout engine, because Uniscribe also uses a
    second
    > interface to the rendering engine (GDI(+), DirectX, and probably
    others
    > possibly in a multi-layered architecture...) and to user-level GUI
    > components (the Windows User API) such as carret management, whose
    > specifications are closed and probably not even standardized across
    > Windows versions.

    The question of standardizing APIs that applications use to draw text is
    completely orthogonal from the question of standardizing the interface
    between software and fonts.

    Peter Constable



    This archive was generated by hypermail 2.1.5 : Thu Aug 25 2005 - 08:21:59 CDT