···<date: 2015-12-18, Friday>···<from: Hans Hagen>···
> On 12/18/2015 7:34 AM, Philipp Gesang wrote:
> > in the old loader, defining a feature containing mixed ligature /
> > substitution causes a crash. Here’s an example:
> >
> >      \enabletrackers [otf.loading]
> >      \startluacode
> >        fonts.handlers.otf.addfeature ("dunno", {
> >            {
> >                type      = "substitution",
> >                data      = { [0x0022] = 0x201D },
> >                prepend   = true,
> >            },
> >            {
> >                type     = "ligature",
> >                data     = { [0x2013] = {0x002D, 0x002D} },
> >                prepend  = true,
> >            },
> >        })
> >        fonts.handlers.otf.features.register {
> >            name        = "dunno",
> >            description = "bug demo",
> >        }
> >      \stopluacode
> >
> >      \definefontfeature [myfeat] [default] [dunno=yes,liga=yes,mode=node]
> >
> >      \definefont [somefont] [file:cmunrm.otf*myfeat]
> >      \starttext
> >        \somefont foo bar " baz
> >      \stoptext
> >
> > This crashes in font-otn on account of a number being indexed.
> > This used to work -- anything that can be done about it?
> 
> i'll see if i can fix it but don't expect all upcoming features in the 
> new loader to work in the old one

Thanks for fixing the crash. However, the substitution doesn’t
work as defined, even if there’s no ligature. It does work with
the TL 2015 version. As it doesn’t seem work with the new loader
either I guess this is related to the “em-dashes not working …”
issue :)

Best,
Philipp