Re: [Devel] OpenType futures

[mpsuzuki]

Dear Mr. Owen,

Could you estimate the size of the unified library of
table-validation + table-parsing + glyph-lookup?

There are several font/printing softwares which does
not require whole of features of OpenType and TrueTypeGX
and using just partial infos provided by the table.

For example, in the scope of CJK text processing,
glyph substitution of vertical writing mode is especially
important, and there is several legacy methods are still
widely used (by using vendor specific char-glyph mapping).
The softwares have to check which vertical writing mode
support is available from the font for first. For such
purpose, full featured OpenType parser looks like overkill.

Regards,

mpsuzuki

Owen Taylor <address@hidden> wrote:

>On Wed, 2004-08-11 at 05:48, Werner LEMBERG wrote:

>Hmm, this doesn't really make sense to me. We have three operations that
>need to know the details about the data structures for individual
>lookups:
> 
> - The code to validate the table
> - The code to parse the table (which is a subset of validation)
> - The code to apply the lookup to glyphs
>
>No matter how we group them it seems a bad idea to put different
>parts of these operations in different libraries. Adding support
>for new lookups or fixing bugs in existing lookups might well
>then require fixes in two places and two releases.