ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in new beta
Date: Mon, 18 Mar 2013 22:03:02 +0100	[thread overview]
Message-ID: <ADA2CEC9-6829-4021-9629-602C874F00C8@gmail.com> (raw)
In-Reply-To: <5147800F.80203@googlemail.com>


Am 18.03.2013 um 21:58 schrieb Xenia <yoraxe@googlemail.com>:

> On 17.03.2013 11:34, Hans Hagen wrote:
>> On 3/17/2013 5:24 AM, Jonathan Barchi wrote:
>> 
>>> Hans (mostly),
>>> 
>>> I've seen that font error too, but it never seemed to cause problems
>>> so I've been ignoring it after I realized that.
>>> 
>>> What I did figure out is that it seems to throw that error the first
>>> time it loads a new font - that is, the first time that a new (known
>>> to mtxrun) font is actually used in a document and loaded into the
>>> cache. The error seems to be due to luatex (? or whatever program does
>>> this) trying to compile a .tma file from the cache into a .tmc file,
>>> but the .tma file doesn't exist. I think it then goes to the .otf
>>> file, loads it, and is OK.
>> 
>> Indeed. I fixed it. It has to do with a test for a tmc file (when we run
>> luajittex I need to make sure that a tmb file is generated as these
>> engines have a different bytecode format). I got rid of the message in
>> the new beta.
> 
> Weird, because I still get this error with

1. Delete the cache and let context regenerate it.

2. When this doesn’t help try it with a clean installation.

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2013-03-18 21:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16 11:35 Xenia
2013-03-16 11:39 ` Hans Hagen
2013-03-16 11:49   ` Xenia
2013-03-16 11:56     ` Hans Hagen
2013-03-16 12:15       ` Xenia
2013-03-17  4:24     ` Jonathan Barchi
2013-03-17 10:34       ` Hans Hagen
2013-03-18 20:58         ` Xenia
2013-03-18 21:03           ` Wolfgang Schuster [this message]
2013-03-18 22:45             ` Xenia
2013-03-16 11:42 ` 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=ADA2CEC9-6829-4021-9629-602C874F00C8@gmail.com \
    --to=schuster.wolfgang@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).