I saved these kerning pairs as a text file, but when I try to use the file with the Autokern feature I don’t get any kerning pairs. Why not?
A” -441 A quotedblright
A’ -441 A quoteright
B” -64 B quotedblright
B’ -64 B quoteright
C” -119 C quotedblright
C’ -119 C quoteright
G” -199 G quotedblright
G’ -199 G quoteright
L” -372 L quotedblright
L’ -372 L quoteright
R” -149 R quotedblright
R’ -149 R quoteright
S” -95 S quotedblright
S’ -95 S quoteright
“A -505 quotedblleft A
“C -87 quotedblleft C
“G -87 quotedblleft G
“M -57 quotedblleft M
“O -81 quotedblleft O
“Q -87 quotedblleft Q
‘A -491 quoteleft A
‘C -73 quoteleft C
‘G -73 quoteleft G
‘O -67 quoteleft O
‘Q -73 quoteleft Q
FontCreator doesn’t support Unicode characters in kerning pair files. This should work:
A\201D -441 A quotedblright
A\2019 -441 A quoteright
B\201D -64 B quotedblright
B\2019 -64 B quoteright
C\201D -119 C quotedblright
C\2019 -119 C quoteright
G\201D -199 G quotedblright
G\2019 -199 G quoteright
L\201D -372 L quotedblright
L\2019 -372 L quoteright
R\201D -149 R quotedblright
R\2019 -149 R quoteright
S\201D -95 S quotedblright
S\2019 -95 S quoteright
\201CA -505 quotedblleft A
\201CC -87 quotedblleft C
\201CG -87 quotedblleft G
\201CM -57 quotedblleft M
\201CO -81 quotedblleft O
\201CQ -87 quotedblleft Q
\2018A -491 quoteleft A
\2018C -73 quoteleft C
\2018G -73 quoteleft G
\2018O -67 quoteleft O
\2018Q -73 quoteleft Q
The kerning export should use the same convention. I’ll make sure that is fixed with the next upcoming release.
Thanks. That works perfectly.