ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sylvain Hubert <champignoom@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How does lua callback work?
Date: Wed, 4 Nov 2020 20:06:28 +0100	[thread overview]
Message-ID: <CACNy3NAs7HEy3LBL-Q=i5ySN_odcDxE9gUxpthZ9BOy2Q9HFAg@mail.gmail.com> (raw)
In-Reply-To: <e879a373-3e26-a4e5-34af-5e522b31f691@xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 474 bytes --]

On Wed, 4 Nov 2020 at 19:25, Hans Hagen <j.hagen@xs4all.nl> wrote:

> no callback
>
> \checkcharactersinfont
>
> will report missing chars
>
Thanks, but this command doesn't seem to add any information on top of the
missing characters that context already reported without the command.

My motivation was to write a module that suggests fallback fonts to the
user, ideally at the moment of encountering a missing character, but at the
end of processing is still acceptable.

[-- Attachment #1.2: Type: text/html, Size: 806 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2020-11-04 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 17:14 Sylvain Hubert
2020-11-04 18:25 ` Hans Hagen
2020-11-04 19:06   ` Sylvain Hubert [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='CACNy3NAs7HEy3LBL-Q=i5ySN_odcDxE9gUxpthZ9BOy2Q9HFAg@mail.gmail.com' \
    --to=champignoom@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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).