[NTG-context] [fontloader/old] mixed substitution / ligatures feature

Hans Hagen pragma at wxs.nl
Fri Dec 18 18:36:04 CET 2015


On 12/18/2015 7:34 AM, Philipp Gesang wrote:
> Hi Hans,
>
> 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

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------


More information about the ntg-context mailing list