ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "talazem@fastmail.fm" <talazem@fastmail.fm>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Upgrade to 2015.11.19 breaks OTF reader?
Date: Fri, 11 Dec 2015 22:51:10 +0000	[thread overview]
Message-ID: <A1E1E77A-9441-4271-B943-4680EA6E531B@fastmail.fm> (raw)
In-Reply-To: <139716C7-AD7B-41B3-AF04-E7C08C3C1B71@fastmail.fm>


[-- Attachment #1.1: Type: text/plain, Size: 3727 bytes --]

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/ `

(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> ]

Talal

> On 10 Dec 2015, at 23:10, talazem@fastmail.fm wrote:
> 
> I am having the same problem as the OP. I have manually edited the font-otr.lua file as per the patch below, and I deleted the font cache. But all to no avail. I still get:
> 
> !LuaTeX error: cannot find OpenType font file for reading ()
>  ==> Fatal error occurred, no output PDF file produced!
> 
> Is there a solution to this?
> 
> Many thanks,
> Talal
> 
>> On 8 Dec 2015, at 00:22, Philipp Gesang <phg@phi-gamma.net <mailto:phg@phi-gamma.net>> wrote:
>> 
>> ···<date: 2015-12-06, Sunday>···<from: Hans Hagen>···
>> 
>>> On 12/6/2015 10:14 PM, Philipp Gesang wrote:
>>>> ···<date: 2015-12-03, Thursday>···<from: Thangalin>···
>>>> 
>>>>> The problem persisted with Courier New, not only Source Sans Pro (SSP).
>>>>> 
>>>>> The font file for Source Sans Pro came directly from the Google's font service.
>>>>> 
>>>>> The SSP (on my machine) works fine in Inkscape.
>>>>> 
>>>>> The exact same font was also working before the ConTeXt upgrade.
>>>> 
>>>> Confirmed, it appears to work if you revert to the old loader in
>>>> font-lib.mkvi.
>>> 
>>> i need a better example of what fails then as it works here
>> 
>> 
>> The problem seems to be the “filename” field being written to the
>> cache from the wrong source. Between the old and the new
>> fontloader, you get the following picture in the “resources”
>> record:
>> 
>>    +  ["filename"]="Everson_Mono_Bold.ttf",
>>    -  ["filename"]="/tmp/here-be-fonts/Everson_Mono_Bold.ttf",
>> 
>> The attached patch fixes it for me.
>> 
>> Philipp
>> 
>> <font-otr.lua-fix-resources.filename.patch>___________________________________________________________________________________
>> If your question is of interest to others as well, please add an entry to the Wiki!
>> 
>> maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> / http://www.ntg.nl/mailman/listinfo/ntg-context <http://www.ntg.nl/mailman/listinfo/ntg-context>
>> webpage  : http://www.pragma-ade.nl <http://www.pragma-ade.nl/> / http://tex.aanhet.net <http://tex.aanhet.net/>
>> archive  : http://foundry.supelec.fr/projects/contextrev/ <http://foundry.supelec.fr/projects/contextrev/>
>> wiki     : http://contextgarden.net <http://contextgarden.net/>
>> ___________________________________________________________________________________
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 7174 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
___________________________________________________________________________________

  parent reply	other threads:[~2015-12-11 22:51 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 [this message]
2015-12-12 10:32                         ` Philipp Gesang

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=A1E1E77A-9441-4271-B943-4680EA6E531B@fastmail.fm \
    --to=talazem@fastmail.fm \
    --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).