Re: [NTG-context] LMTX: request for \tracinglostchars=3
Hans Hagen via ntg-context writes: >> LMTX only seems to support =0 (ignore) and =1 (report). Making these >> a fatal error (with exit status != 0) would be useful for automated >> typesetting, as missing characters easily can get lost in the logs, >> and then symbols are missing unnoticed in the output. > > Will never be default, you can play with: > > % \checkmissingcharacters > % \removemissingcharacters > % \replacemissingcharacters > % \handlemissingcharacters > >> (However, \tracinglostchars=3 also doesn't seem to work with >> LuaTeX+MKIV, probably because there is code to fallback to other fonts?) > and if you want to quit: > > \enabledirectives[logs.errors=missing characters] Ok, this is useful. I looked around, but I couldn't find a similar feature for when a font is not found? cu, -- Leah Neukirchenhttps://leahneukirchen.org/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] LMTX: request for \tracinglostchars=3
On 12/22/2022 4:23 PM, Leah Neukirchen via ntg-context wrote: Hi, since TeX Live 2021 (TeX 3.141592653), there is - if \tracinglostchars >= 3, make missing characters an error (not just a log message), and always report the character code in hex. LaTeX also enables this by default these days. Not really our reference -) LMTX only seems to support =0 (ignore) and =1 (report). Making these a fatal error (with exit status != 0) would be useful for automated typesetting, as missing characters easily can get lost in the logs, and then symbols are missing unnoticed in the output. Will never be default, you can play with: % \checkmissingcharacters % \removemissingcharacters % \replacemissingcharacters % \handlemissingcharacters (However, \tracinglostchars=3 also doesn't seem to work with LuaTeX+MKIV, probably because there is code to fallback to other fonts?) and if you want to quit: \enabledirectives[logs.errors=missing characters] Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] LMTX: request for \tracinglostchars=3
Hi, since TeX Live 2021 (TeX 3.141592653), there is > - if \tracinglostchars >= 3, make missing characters an error (not just > a log message), and always report the character code in hex. LaTeX also enables this by default these days. LMTX only seems to support =0 (ignore) and =1 (report). Making these a fatal error (with exit status != 0) would be useful for automated typesetting, as missing characters easily can get lost in the logs, and then symbols are missing unnoticed in the output. (However, \tracinglostchars=3 also doesn't seem to work with LuaTeX+MKIV, probably because there is code to fallback to other fonts?) cu, -- Leah Neukirchenhttps://leahneukirchen.org/ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
