From: Philipp Gesang <phg@phi-gamma.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Upgrade to 2015.11.19 breaks OTF reader?
Date: Sat, 12 Dec 2015 11:32:52 +0100 [thread overview]
Message-ID: <20151212103252.GC313@phlegethon> (raw)
In-Reply-To: <A1E1E77A-9441-4271-B943-4680EA6E531B@fastmail.fm>
[-- Attachment #1.1: Type: text/plain, Size: 1457 bytes --]
···<date: 2015-12-11, Friday>···<from: talazem@fastmail.fm>···
> In case this helps anyone else:
>
> In my case, the LuaTeX error resulted from what appears to be a corrupt font cache. I was getting the error:
>
> > !LuaTeX error: cannot find OpenType font file for reading ()
> > ==> Fatal error occurred, no output PDF file produced!
>
> The solution was to clean the LuaTeX font cache in my ConTeXt standalone directory. Mine was in:
> ` ~/context/tex/texmf-cache/luatex-cache/context/<...>/fonts/otf/ `
You can use ``mtxrun --script cache --erase`` for that.
> (The <…> represents a long string of numbers.)
>
> I deleted the .tma and .tmc files in that OTF directory. Upon running ConTeXt again, everything worked fine. [The source of this discovery was http://tex.stackexchange.com/questions/65038/luatex-cannot-find-existing-font <http://tex.stackexchange.com/questions/65038/luatex-cannot-find-existing-font> ]
I’ve run my tests explicitly erasing the caches (not only the
fonts one) and rebuilding both the format and the file indices
every time.
Try this:
export OSFONTDIR=~/.fonts
mtxrun --script cache --erase && mtxrun --generate && context --make && mtxrun --script fonts --reload && context source.tex
(Adapt the OSFONTDIR path and replace “source.tex” with the name
of your test file.) Make sure there’s no copy of the font in PWD
or the system path.
Best,
Philipp
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2015-12-12 10:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 23:36 Thangalin
2015-12-02 23:41 ` Thangalin
2015-12-03 0:14 ` Thangalin
2015-12-03 7:27 ` Philipp Gesang
2015-12-03 13:35 ` Hans Hagen
2015-12-03 17:39 ` Philipp Gesang
2015-12-03 21:29 ` Hans Hagen
2015-12-04 2:39 ` Thangalin
2015-12-06 21:14 ` Philipp Gesang
2015-12-06 21:44 ` Hans Hagen
2015-12-08 0:22 ` Philipp Gesang
2015-12-10 23:10 ` talazem
2015-12-11 9:15 ` talazem
2015-12-11 22:51 ` talazem
2015-12-12 10:32 ` Philipp Gesang [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=20151212103252.GC313@phlegethon \
--to=phg@phi-gamma.net \
--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).