* LMTX: request for \tracinglostchars=3
@ 2022-12-22 15:23 Leah Neukirchen via ntg-context
2022-12-22 15:39 ` Hans Hagen via ntg-context
0 siblings, 1 reply; 3+ messages in thread
From: Leah Neukirchen via ntg-context @ 2022-12-22 15:23 UTC (permalink / raw)
To: ntg-context; +Cc: Leah Neukirchen
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 Neukirchen <leah@vuxu.org> https://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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: LMTX: request for \tracinglostchars=3
2022-12-22 15:23 LMTX: request for \tracinglostchars=3 Leah Neukirchen via ntg-context
@ 2022-12-22 15:39 ` Hans Hagen via ntg-context
2022-12-22 18:23 ` Leah Neukirchen via ntg-context
0 siblings, 1 reply; 3+ messages in thread
From: Hans Hagen via ntg-context @ 2022-12-22 15:39 UTC (permalink / raw)
To: ntg-context; +Cc: Hans Hagen
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: LMTX: request for \tracinglostchars=3
2022-12-22 15:39 ` Hans Hagen via ntg-context
@ 2022-12-22 18:23 ` Leah Neukirchen via ntg-context
0 siblings, 0 replies; 3+ messages in thread
From: Leah Neukirchen via ntg-context @ 2022-12-22 18:23 UTC (permalink / raw)
To: ntg-context; +Cc: Leah Neukirchen
Hans Hagen via ntg-context <ntg-context@ntg.nl> 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 Neukirchen <leah@vuxu.org> https://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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-12-22 18:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-22 15:23 LMTX: request for \tracinglostchars=3 Leah Neukirchen via ntg-context
2022-12-22 15:39 ` Hans Hagen via ntg-context
2022-12-22 18:23 ` Leah Neukirchen via ntg-context
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).