[ft-devel] Re: [PATCH] Fix SEAC glyphs with the incremental interface

[Werner LEMBERG]

> Please take a look at the attached patch to make accented characters
> work with the incremental font interface Ghostscript uses.  The
> patch is gs-specific, but we'd like to get this resolved upstream
> somehow.

I'll apply it as-is, thanks.

> Basically, the implementation of the type 1 single encoding accented
> glyph operator tries to look up the referenced glyph indices before
> constructing the composite glyph.  We don't pass the decoding in
> when using the incremental interface, so this fails.  And indeed,
> the check is prefaced with a comment:
>
>      /* `glyph_names' is set to 0 for CID fonts which do not */
>      /* include an encoding.  How can we deal with these?    */
>
> Our patch just disables the check if the incremental font interface
> is compiled in, which I doubt is satisfactory.  How should this be
> handled?

I don't know either :-)  However, your explanation in the fix seems to
be right.

> It works fine if the code assumes an identity mapping.  I'm confused
> how responsibility was intended to be divided here; the API
> Reference says, "Apart from [glyphs], all other tables are loaded
> normally from the font file.  This mode is useful when FreeType is
> used within another engine, e.g., a PostScript Imaging Processor."
> I don't understand how that's intended to work when there is no
> literal font file.

Graham, can you explain?


    Werner