![](https://secure.gravatar.com/avatar/e1d6b7d0f096cb8cf44273fa33fb05f0.jpg?s=120&d=mm&r=g)
···
On 8/4/2013 3:43 PM, Philipp Gesang wrote:
Hi Hans,
this is a bug report thanks to Khaled:
http://tex.stackexchange.com/a/126650/14066
In short: the font loader applies the kerning of libertine version 5.3.0 even though this appears to be broken in the font. Context translation of the example:
\definefontfeature [kerning] [mode=node,smcp=yes,kern=yes] \definefont [libertineserifsmallcaps] [file:LinLibertine_R.otf*kerning] \definefont [libertinesanssmallcaps] [file:LinBiolinum_R.otf*kerning]
\def\demotext{Vacillate Vaccine Vapour Vanish Va...}
\starttext {\libertineserifsmallcaps \demotext}\par {\libertinesanssmallcaps \demotext}\par \stoptext
(Doesn’t occur in base mode.) The technical details are in the thread Khaled references.
\showotfcomposition{file:LinLibertine_R.otf*kerning}{+1}{Va} \page \showotfcomposition{file:LinBiolinum_R.otf*kerning} {+1}{Va} \page
You need to be more explicit (which font, where to download the problematic one, etc ... i downloaded the 5.3 version - i think - of ll). In what sense is it broken in the font?
It’s that version (5.3.0). To quote Jonathan Kew [1]:
The problem arises because the first subtable includes the
"V" (and "T") glyphs in its coverage (as first glyph of the
pair), but then the a.sc and hyphen.sc glyphs are not
included in the ClassDef2 table, so they map to class 0, for
which the kerning is zero. [...]
The description of ClassDefFormat2 says that "Any glyph not
covered by a ClassRangeRecord is assumed to belong to Class
0". If that is the case, then I think this is a font bug: any
first-glyph mentioned in a PairPosFormat2 subtable's coverage
when ClassDef2 uses format 2 will, in effect, "shadow" all
subsequent subtables, so the same first-glyph cannot be used
again.
And the follow up [2]:
FWIW, testing LinLibertine in IE10 on Win8, I see the same
behavior as in Firefox (using harfbuzz): the