>>> AFAIK, the code in luatex to handle OpenType features (in 'node'
>>> mode) was derived from FontForge.
>>
>> Luigi and Hans will correct me if I'm wrong here, but I don't
>> believe that this is the case.
>
> But indeed you're right (as usual).
Thanks, Hans and Max, for the clarification.
> Wrt to this somewhat weird thread about marks and fixing a cached
> font then to be recached (likely less efficient) while it can be
> done runtime (at no cost and efficiently) ...
I don't understand what you say, please elaborate. What exactly is
'runtime' and what is not? What structures are you referring to? It
seems that I don't get the big picture here.
> assuming that slot 50 has something is a bad idea ... in my case
> (context) it's in slot 53 and even then one has to descend one level
> more to reach the hit
>
> 53 1 1 65 335 -30
> 53 1 2 65 363 675
> 53 1 3 65 0 0
> 53 1 4 65 0 0
>
> [...] the only reason i checked it that there was this "discoverd a
> bug" mentioning so i checked the code and so it looked like i wasted
> over an hour
Oops! You are right, the `baseclasses` entries for glyph 65 are
present. I don't know how I could have missed them. Sorry for the
noise and your extra work.
Werner
