From: S Barmeier <severinbarmeier@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX error after update to ubuntu 12.04
Date: Sat, 28 Apr 2012 14:10:33 +0900 [thread overview]
Message-ID: <4F9B7BC9.4080607@googlemail.com> (raw)
In-Reply-To: <1335587439.3883.5.camel@kip-laptop>
Deleting the cache worked, thank you! The first run on my book
successfully compiled after 7 mins., subsequent ones now take 15
seconds (which used to be a stable 25 sec before the upgrade).
In ubuntu 12.04 all font packages are renamed to fonts-*, rather than
ttf-* or otf-* etc.
I thought that running mtxrun --script fonts --reload would fix lookup
problems, but it seems that you might want to clear the cache completely.
Still, esp. with the added speed benefit, there is no reason to hold
back the upgrade (from my point of view).
Thanks,
Severin
On 04/28/2012 01:30 PM, Kip Warner wrote:
> On Sat, 2012-04-28 at 13:25 +0900, S Barmeier wrote:
>> After updating to ubuntu 12.04, my shouts of joy were smothered
>> by the following
>>
>> !LuaTeX error: cannot find OpenType font file for reading () ==>
>> Fatal error occurred, no output PDF file produced!
>
> Fuuuuuuck...and here I was planning on upgrading tomorrow morning.
>
___________________________________________________________________________________
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:[~2012-04-28 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 4:25 S Barmeier
2012-04-28 4:30 ` Kip Warner
2012-04-28 5:10 ` S Barmeier [this message]
2012-04-29 20:28 ` Kip Warner
2012-04-29 21:41 ` Khaled Hosny
2012-04-28 4:40 ` Khaled Hosny
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=4F9B7BC9.4080607@googlemail.com \
--to=severinbarmeier@googlemail.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).