From: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Leah Neukirchen <leah@vuxu.org>
Subject: LMTX: request for \tracinglostchars=3
Date: Thu, 22 Dec 2022 16:23:09 +0100 [thread overview]
Message-ID: <87fsd7pin6.fsf@vuxu.org> (raw)
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
___________________________________________________________________________________
next reply other threads:[~2022-12-22 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 15:23 Leah Neukirchen via ntg-context [this message]
2022-12-22 15:39 ` Hans Hagen via ntg-context
2022-12-22 18:23 ` Leah Neukirchen via ntg-context
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsd7pin6.fsf@vuxu.org \
--to=ntg-context@ntg.nl \
--cc=leah@vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).