ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Denis Maier via ntg-context <ntg-context@ntg.nl>
To: <ntg-context@ntg.nl>
Cc: denis.maier@unibe.ch
Subject: Re: Understanding font errors
Date: Fri, 26 Aug 2022 20:22:54 +0000	[thread overview]
Message-ID: <f9d8526e2dbf432ea6b52c517496a939@unibe.ch> (raw)
In-Reply-To: <708e2df7-683d-2bf4-6c84-0412ad09f8a8@freedom.nl>

> -----Ursprüngliche Nachricht-----
> Von: ntg-context <ntg-context-bounces@ntg.nl> Im Auftrag von Hans Hagen
> via ntg-context
> Gesendet: Freitag, 26. August 2022 22:11
> An: ntg-context@ntg.nl
> Cc: Hans Hagen <j.hagen@freedom.nl>
> Betreff: Re: [NTG-context] Understanding font errors
> 
> On 8/26/2022 10:07 PM, Denis Maier via ntg-context wrote:
> > Hi,
> > I've just noticed I'm getting error messages related to fonts:
> >
> > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > fonts           > checking > char G (U+00047) in font '' with id 0: missing
> > fonts           > checking > char r (U+00072) in font '' with id 0: missing
> > fonts           > checking > char a (U+00061) in font '' with id 0: missing
> > fonts           > checking > char f (U+00066) in font '' with id 0: missing
> > fonts           > checking > char i (U+00069) in font '' with id 0: missing
> > fonts           > checking > char k (U+0006B) in font '' with id 0: missing
> > fonts           > checking > char [space] in font '' with id 0: missing
> > fonts           > checking > char m (U+0006D) in font '' with id 0: missing
> > fonts           > checking > char t (U+00074) in font '' with id 0: missing
> > fonts           > checking > char L (U+0004C) in font '' with id 0: missing
> > fonts           > checking > char b (U+00062) in font '' with id 0: missing
> > fonts           > checking > char e (U+00065) in font '' with id 0: missing
> > fonts           > checking > char l (U+0006C) in font '' with id 0: missing
> > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> >
> > What exactly is that supposed to mean? There does not seem to be a
> problem in the resulting PDFs. What should I do to debug this?
> you probably have that text before you load a font (so it's nullfont)
> 
> search for that text ... "grafik "

Thanks. I've done that already ... but apparently in the wrong file. "grafik" does not appear in file containing the text, which is why I was confused. But it appears in the environment file in a line that should be a comment.

Thanks again,
Denis

___________________________________________________________________________________
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-08-26 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 20:07 Denis Maier via ntg-context
2022-08-26 20:11 ` Hans Hagen via ntg-context
2022-08-26 20:22   ` Denis Maier via ntg-context [this message]
2022-08-26 21:28     ` Henning Hraban Ramm 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=f9d8526e2dbf432ea6b52c517496a939@unibe.ch \
    --to=ntg-context@ntg.nl \
    --cc=denis.maier@unibe.ch \
    /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).