As far as kerning is concerned, for the existing TTF and OTF support,
positioning is handled at the TextLayoutManager layer in combination with
rendering instructions through the IF rendering layer. Prior to
Temp_ComplexScripts (and current in the trunk), kerning is performed only
when a 'kern' table is present and has not been disabled. With the addition
of the GPOS table support in Temp_ComplexScripts, a very rich set of
context-sensitive kerning (in both X and Y axes) is supported. If a font has
a GPOS table, then any 'kern' table is ignored.
>From what I can tell, the CFF data primarily is related to outline
presentations, which themselves have no relationship to kerning per se. So,
the question seems one of how to employ the CFF outline representations in
an OTF/CFF context, and how to pass through that outline data for embedding
in the resultant PDF. Is that your understanding as well?
On Fri, Mar 4, 2011 at 12:12 AM, Alex Zepeda <zipzi...@sonic.net> wrote:
> Glenn Adams wrote:
>> It may be useful to wait until the Temp_ComplexScripts branch is merged
>> into trunk to decide how to proceed with CFF. It is possible my client would
>> like me to take a stab at CFF, so I may be able to add that to my task list.
> Perhaps. Exposing the CFF data is trivial tho. It's knowing what to do
> with it (ex: parsing the charstrings to get extended kerning info) that's
> more difficult. Right now I'm thinking I should be able to take the glyph
> (name to gid) index and create a Type1-esque cmap. I've already got the
> code to parse indexes (incl. the gid to glyph name one), so.
> What sort of timeframe were you looking at for completing the
> Temp_ComplexScripts branch?
> - alex