Glenn Adams commented on FOP-2213:

As Luis says, see also TextLayoutManager#processWordMapping, especially:

    // 4. compute glyph position adjustments on (substituted) characters        
        int[][] gpa;
        if ( font.performsPositioning() ) {
            // handle GPOS adjustments                                          
            gpa = font.performPositioning ( mcs, script, language );
        } else if ( font.hasKerning() ) {
            // handle standard (non-GPOS) kerning adjustments                   
            gpa = getKerningAdjustments ( mcs, font );
        } else {
            gpa = null;

font.performsPositioning() when CS is enabled and the font contains at least 
one GPOS subtable in the GPOS table; if some GPOS subtable applies, then the CS 
path assumes that the font designer will include a subtable mapped to the 
'kern' feature [1]

[1] http://www.microsoft.com/typography/otspec/features_ko.htm#kern

it is up the font designer to program the GPOS feature table to contain the 
desired subtables

i also notice the following warning under then non-GPOS (older) 'kern' table 
(do not confuse this with the 'kern' feature of the GPOS table) [2]:

OpenType™ fonts containing CFF outlines are not supported by the 'kern' table 
and must use the 'GPOS' OpenType Layout table.

[2] http://www.microsoft.com/typography/otspec/kern.htm

what I suspect is happening in the current case is that the font author 
includes some GPOS table (but not one containing a subtable mapped to the 
'kern' feature) and also includes a 'kern' table;

i wonder if there is a newer version of the font that fixes this
> Kerning is no longer applied
> ----------------------------
>                 Key: FOP-2213
>                 URL: https://issues.apache.org/jira/browse/FOP-2213
>             Project: Fop
>          Issue Type: Bug
>          Components: fonts
>    Affects Versions: 1.1, trunk
>            Reporter: Vincent Hennebert
>         Attachments: fop.xconf, kerning_1.0.pdf, kerning_1.1.pdf, kerning.fo, 
> kerning-v2_1.1-cs.pdf, kerning-v2_1.1-nocs.pdf, kerning-v2.fo
> See attached example. With FOP 1.0 the dot can be seen 'inside' the Y glyph 
> as expected, while it's not the case with FOP 1.1.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to