ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
To: <ntg-context@ntg.nl>
Cc: Leah Neukirchen <leah@vuxu.org>
Subject: Re: LMTX: request for \tracinglostchars=3
Date: Thu, 22 Dec 2022 19:23:53 +0100	[thread overview]
Message-ID: <87bknvpa9y.fsf@vuxu.org> (raw)
In-Reply-To: <315092b8-5414-2edd-cc9e-c1a4f421d031@freedom.nl> (Hans Hagen via ntg-context's message of "Thu, 22 Dec 2022 16:39:39 +0100")

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
___________________________________________________________________________________

      reply	other threads:[~2022-12-22 18: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
2022-12-22 15:39 ` Hans Hagen via ntg-context
2022-12-22 18:23   ` Leah Neukirchen via ntg-context [this message]

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=87bknvpa9y.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).