Kerning tables in .fea files

[Adam Baker-7]

I have been doing pairwise kerning, saving the result to a feature
file (.fea) in order to edit it, and then reloading the table into the
font later. (I am removing everything except the kerning table in the
feature file, saving it, and then using the "Merge Feature Info"
command.) This works, perhaps one time in four. There is apparently
something going on that I do not understand. :-)

When I examine my feature files, at different points I get the
following kinds of lines of output.

(1)    pos \uni0631  < 0 0 0 0 > \uni0627 < 0 0 -154 0 >;

(2)    pos \uni0627 <0 0 0 -122 <device NULL> <device NULL> <device
NULL> <device NULL>> \uni06BA  <0 0 0 -122 <device NULL> <device NULL>
<device NULL> <device NULL>>;

(3)    pos \uni0631 \uni0627 -486;

When (2) appears in the feature file, kerning never works. I have
imported feature files that look like (1) which, if I then re-export,
looks like (2).

I realize I am providing very little to go on. Is this kind of
behavior reminiscent of something anybody else has dealt with?

Thanks,
Adam

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Fontforge-users mailing list
Fontforge-users@...
https://lists.sourceforge.net/lists/listinfo/fontforge-users

[Barry Schwartz-2]

Adam Baker <adamb924@...> skribis:

> I have been doing pairwise kerning, saving the result to a feature
> file (.fea) in order to edit it, and then reloading the table into the
> font later. (I am removing everything except the kerning table in the
> feature file, saving it, and then using the "Merge Feature Info"
> command.) This works, perhaps one time in four. There is apparently
> something going on that I do not understand. :-)
>
> When I examine my feature files, at different points I get the
> following kinds of lines of output.
>
> (1)    pos \uni0631  < 0 0 0 0 > \uni0627 < 0 0 -154 0 >;

This one looks unusual but is equivalent to form (3).

> (2)    pos \uni0627 <0 0 0 -122 <device NULL> <device NULL> <device
> NULL> <device NULL>> \uni06BA  <0 0 0 -122 <device NULL> <device NULL>
> <device NULL> <device NULL>>;

This is calling for vertical advances, which I imagine is not what you
wanted.

> (3)    pos \uni0631 \uni0627 -486;

This is the usual notation. :)

Here is the spec:
http://www.adobe.com/devnet/opentype/afdko/topic_feature_file_syntax.html


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Fontforge-users mailing list
Fontforge-users@...
https://lists.sourceforge.net/lists/listinfo/fontforge-users