From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Spurious missing character log messages
Date: Thu, 17 Apr 2014 08:51:23 +0200 [thread overview]
Message-ID: <534F79EB.30205@wxs.nl> (raw)
In-Reply-To: <534F257E.9030802@rik.users.panix.com>
On 4/17/2014 2:51 AM, Rik Kabel wrote:
> It appears that descriptions generate a spurious
>
> Missing character: There is no ^@ (U+0000) in font lmroman12-regular!
>
> log message. MWE:
>
> \definedescription[oops][]
> \starttext
> \oops{Where}is the U+0000?
> \stoptext
>
> The messages appears in the log once for each description in the document.
>
> This happens with the current (2014-04-15) beta. It does not happen with
> TL13.
In \CONTEXT\ we sometimes use U+0000 as signal. It looks like we need a
callback for intercepting such messages in the log.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-04-17 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 0:51 Rik Kabel
2014-04-17 6:51 ` Hans Hagen [this message]
2014-04-17 9:14 ` Hans Hagen
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=534F79EB.30205@wxs.nl \
--to=pragma@wxs.nl \
--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).