[NTG-context] Another bug with ligature-blocking?

Hans Hagen j.hagen at xs4all.nl
Wed Mar 24 17:41:58 CET 2021


On 3/24/2021 4:48 PM, denis.maier at ub.unibe.ch wrote:

> \definefontfamily[times][rm][Times New Roman]
don't assume beforehand that something that doesn't work as expected is 
a bug

the font just has no ligatures defined which you can remedy (in this 
cae) with because it does have the glyphs

\startluacode
     fonts.handlers.otf.addfeature {
         name = "moreligatures",
         type = "ligature",
         data = {
             ['ff'] = { "f", "f" },
             ['fi'] = { "f", "i" },
             ['fl'] = { "f", "l" },
         }
     }
\stopluacode


\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
\definefontfamily[times][rm][Times New Roman]
\definefontfamily[termes[rm][TeX Gyre Termes]

\definefontfeature[default:block][default][blockligatures=yes]

\starttext

{\switchtobodyfont[times] \definedfont[Serif*default]        begrifflich 
ff fi fl\blank
                           \definedfont[Serif*default:block] 
begrifflich ff fi fl\blank}
{\switchtobodyfont[termes]\definedfont[Serif*default]        begrifflich 
ff fi fl\blank
                           \definedfont[Serif*default:block] 
begrifflich ff fi fl\blank}

\stoptext



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


More information about the ntg-context mailing list