Re: Possible bug in \definefontfallback with check=yes
Jean-Pierre Delange via ntg-context <[email protected]>
| Newsgroups | gmane.comp.tex.context |
|---|---|
| Message-ID | <[email protected]> |
Hi Wolfgang, Many thanks for looking into this and for locating the problem. This matches the behaviour I observed in the Syriac fallback tests: with |force=yes| the fallback vector was built correctly, whereas adding |check=yes| prevented the expected Syriac fallback from being used. I will retest the original MWE once the correction to |font-col.lmt| is available in an updated ConTeXt distribution. Best, JP Le 15/08/2026 à 12:53, Wolfgang Schuster a écrit : > Am 13.08.2026 um 09:51 schrieb Hans Hagen via ntg-context: >> On 8/13/2026 9:15 AM, Jean-Pierre Delange via ntg-context wrote: >>> Hi Hans, >>> >>> While testing Semitic languages for multilingual bibliography support >>> (in this case Aramaic/Syriac), I came across a reproducible problem >>> with >>> `check=yes` in `\definefontfallback`. >> >> hopefully Wolfgang can have a look at it as I'm in the middle of >> something else so switching to font mode ... otherwise it has to wait >> a couple of days. > > I took a look at it and line 301 in font-col.lmt has to changed from > > elseif not newchars[target] then > > to > > elseif not newchars[unic] then > > Wolfgang ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : [email protected] / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___________________________________________________________________________________