Welcome to Typophile
Please Sign in.

Annoying message in FL5 class kerning

Primary tabs

7 posts / 0 new
Last post
seneca's picture
Joined: 19 Aug 2007 - 11:32pm
Annoying message in FL5 class kerning

I'm new to class kerning, I read the Cabarga book step by step, read the confusing FL5 manual as well, made some classes, made the kern feature as indicated (which I put after the liga feature) updated it, and apparently everything was going fine, but after some more pairs, on compiling and/or generating, I get this annoying (and worrying) message:

"Start of new pair positioning subtable; some pairs may never be accessed: etc etc"

I read some threads trying to find out about this and someone suggested inserting a "subtable;" line every 100 lines or so in the kern feature. I did this also but when I export my PS flavoured OT font, once more there's the message! (grrr!)

Anyone knows why this is? I know this might be quite a basic thing for most of you but I'm really going nuts trying to find out what it was that I did wrong, or else I'll have to stick to my very dated way: manual kerning and simple TT and PS formats and shame for the great ligatures, alternates and so on...

I'd really appreciate your help here, I hope this is something simple and I'm only drowning in a glass of water... Thanks!

Göran Söderström's picture
Joined: 15 Feb 2006 - 2:53am

I think there is something wrong with your classes. Maybe some glyph are represented two times in a conflicting way or something like that, making it impossible to access some pairs, if you perhaps have two "commands" for this glyph.

My suggestion is that you triple-check that all classes are flagged (right/left) correctly in the class-panel. That is, make sure the classes are logical when it comes to deciding which is the first glyph in a pair, and which is the second.

Did that make sense?

Miguel Sousa's picture
Joined: 18 May 2003 - 8:30pm

> “Start of new pair positioning subtable; some pairs may never be accessed: ...”

This message usually appears when a given glyph is contained in more than one kern class. What triggers the message is when these classes — that have a glyph in common — are used on the same side of two or more class kern pairs (within the same subtable). E.g.:

feature kern {
@_B_LC = [b];
@_O_LC = [o oacute];
@_ROUND_LC_LEFT = [o b];

pos @_B_LC @_O_LC -20;
pos @_ROUND_LC_LEFT @_O_LC -30;
} kern;

The example above generates the following message:
[WARNING] Start of new pair positioning subtable; some pairs may never be accessed: [b o] [o oacute]

The warning means that some pairs downstream (second 'pos') are being masked by pairs defined upstream (first 'pos'). Effectively, these two class kern pairs are equivalent to the following singleton pairs,

pos b o -20;
pos b oacute -20;

pos o o -30;
pos o oacute -30;
pos b o -30;
pos b oacute -30;

where it becomes clear that there are conflicting/repeated 'pos' commands. (BTW, pairs defined upstream take precedence).

All this to say that, as a rule of thumb, each glyph should only be included in one left kern class, and one right kern class, maximum. (This is by no means a strict rule, but you'll save yourself a few headaches if you follow it)

seneca's picture
Joined: 19 Aug 2007 - 11:32pm

Goran and Miguel: Thanks a lot for your tips, everything glided goldenly following them! Thing is I get too stressed out, and for no reason.

froo's picture
Joined: 2 Jun 2008 - 5:19am

I had the same problem on FL 5.0.4 (Win). It made me sick, because all classes were well prepared. Then I discovered, that Assistance reported a glyph duplicated in two classes, and one of them was removed previous day. So I understood that the bug may come from file "memory".
I saved my classes, deleted them (and the kern feature), closed the program, launched again and imported the saved classes. Voila! No bad report!

7roy's picture
Joined: 15 Aug 2009 - 2:10am

Try 'Clean Up Classes' under the disk icon in your classes window. This worked for me.

Russell McGorman's picture
Joined: 25 May 2006 - 10:01am

thanks from me too... I was about the ask the same question.