Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Philipp Gesang]

·

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

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



pgpMuDKFYv2x0.pgp
Description: PGP signature
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[tala...@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/ `

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

Talal

> On 10 Dec 2015, at 23:10, tala...@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 > > wrote:
>> 
>> ·
>> 
>>> On 12/6/2015 10:14 PM, Philipp Gesang wrote:
 ·
 
> 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
>> 
>> ___
>> 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 
>> ___
> 
> ___
> 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
> ___

___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[tala...@fastmail.fm]

If I copy the fonts I need into ~/Library/Fonts/, the latest beta is able to 
produce the PDF without the aforementioned Luatex error. 

However, there still seems to be some type of OTF-related error: certain glyphs 
are being replaced with others. This is particularly true for diacritics, but 
not exclusively — all caps are also facing similar problems. I have attached 
some screen clippings to demonstrate.

If I revert back to an earlier beta (as of September 2015) it does do not cause 
this problem. 


(should read: PROFESSIONAL AND SCHOLARLY LIFE)


(should read: -Thaqāfah)


(should read: aḥwāl)

> On 10 Dec 2015, at 23:10, tala...@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 > > wrote:
>> 
>> ·
>> 
>>> On 12/6/2015 10:14 PM, Philipp Gesang wrote:
 ·
 
> 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
>> 
>> ___
>> 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 
>> ___
> 
> ___
> 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
> ___

___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[tala...@fastmail.fm]

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  wrote:
> 
> ·
> 
>> On 12/6/2015 10:14 PM, Philipp Gesang wrote:
>>> ·
>>> 
 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
> 
> ___
> 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
> ___

___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Philipp Gesang]

·

> On 12/6/2015 10:14 PM, Philipp Gesang wrote:
> > ·
> >
> >> 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.orig	2015-12-08 01:18:18.161761832 +0100
+++ font-otr.lua	2015-12-08 01:18:25.901761761 +0100
@@ -1954,7 +1954,7 @@
 hasitalics = fontdata.hasitalics or false,
 },
 resources = {
-filename  = fontdata.filename,
+filename  = filename,
 private   = privateoffset,
 duplicates= fontdata.duplicates  or { },
 features  = fontdata.featuresor { }, -- we need to add these in the loader


pgpPzmq76nuly.pgp
Description: PGP signature
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Philipp Gesang]

·

> 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.



pgpjuf_H01nVk.pgp
Description: PGP signature
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Hans Hagen]

On 12/6/2015 10:14 PM, Philipp Gesang wrote:

·


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

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Hans Hagen]

On 12/3/2015 8:27 AM, Philipp Gesang wrote:

·
 fonts   > otf loading > loading done
 fonts   > otf loading > saving 
'/home/phg/.fonts/OTF/adobe-source/SourceSansPro-Regular.otf' in cache
 system  > lua > compiling 
'/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma'
 into 
'/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc'
 system  > lua > dumping 
'/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma'
 into 
'/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc'
 stripped
 fonts   > otf loading > loading, optimizing, packing and caching 
time 0.569
 fonts   > defining > source file 'SourceSansPro-Regular.otf' is 
not found
 …
 close source> 2 > 3 > /tmp/ctx/fnt.tex
 close source> 1 > 3 > 
/home/phg/context/tex/texmf-context/tex/context/base/cont-yes.mkiv


is there a tma/tmc file?


 !LuaTeX error: cannot find OpenType font file for reading ()
  ==> Fatal error occurred, no output PDF file produced!

Log attached. Bug?

Best,
Philipp



___
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
___




--

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Philipp Gesang]

·

> On 12/3/2015 8:27 AM, Philipp Gesang wrote:
> > ·
> >  fonts   > otf loading > loading done
> >  fonts   > otf loading > saving 
> > '/home/phg/.fonts/OTF/adobe-source/SourceSansPro-Regular.otf' in cache
> >  system  > lua > compiling 
> > '/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma'
> >  into 
> > '/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc'
> >  system  > lua > dumping 
> > '/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma'
> >  into 
> > '/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc'
> >  stripped
> >  fonts   > otf loading > loading, optimizing, packing and 
> > caching time 0.569
> >  fonts   > defining > source file 'SourceSansPro-Regular.otf' 
> > is not found
> >  …
> >  close source> 2 > 3 > /tmp/ctx/fnt.tex
> >  close source> 1 > 3 > 
> > /home/phg/context/tex/texmf-context/tex/context/base/cont-yes.mkiv
> 
> is there a tma/tmc file?

Apparently:

$ ls 
/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tm*

/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma

/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc

It’s valid Lua, too.

Philipp



pgp9UM3Dnx_nS.pgp
Description: PGP signature
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Hans Hagen]

On 12/3/2015 6:39 PM, Philipp Gesang wrote:

·


On 12/3/2015 8:27 AM, Philipp Gesang wrote:

·
  fonts   > otf loading > loading done
  fonts   > otf loading > saving 
'/home/phg/.fonts/OTF/adobe-source/SourceSansPro-Regular.otf' in cache
  system  > lua > compiling 
'/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma'
 into 
'/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc'
  system  > lua > dumping 
'/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma'
 into 
'/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc'
 stripped
  fonts   > otf loading > loading, optimizing, packing and caching 
time 0.569
  fonts   > defining > source file 'SourceSansPro-Regular.otf' is 
not found
  …
  close source> 2 > 3 > /tmp/ctx/fnt.tex
  close source> 1 > 3 > 
/home/phg/context/tex/texmf-context/tex/context/base/cont-yes.mkiv


is there a tma/tmc file?


Apparently:

 $ ls 
/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tm*
 
/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma
 
/home/phg/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc

It’s valid Lua, too.


strange ... i know that there are broken sourcesans around (i now only 
have the ttc on my machine) as it became a real mess of fonts (otf / ttf 
/ttc)


Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[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.
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Thangalin]

The answer from a SE question has provided a little light:

http://tex.stackexchange.com/q/274582/2148

Directories listed in OSFONTDIR are not recursively scanned for font
files. That's a bit inconvenient. I borrowed from the answer in that
question to do the following:

rm -rf $HOME/.fonts
mkdir $HOME/.fonts
cd $HOME/.fonts
for i in $(echo $OSFONTDIR | sed -e 's/:/ /g') ; do for j in $(find $i
-type f); do ln -s $j .; done; done

The last line creates a symbolic link to every font file specified by
OSFONTDIR. This is means that adding new fonts requires re-linking
them to $HOME/.fonts.

After that, I set OSFONTDIR as follows in $HOME/.bashrc:

OSFONTDIR=$HOME/.fonts

Then:

mtxrun --script fonts --reload

After that, ConTeXT produced the PDF for the MWE at the start of this thread.

How can OSFONTDIR be recursed again?

FWIW, I tried:

OSFONTDIR=/usr/share/fonts//:/usr/local/share/fonts//:/usr/share/texmf/fonts/opentype//:/usr/share/fonts/type1/gsfonts//

That didn't work, either.
___
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
___

[NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Thangalin]

Hi.

Installation: 
http://wiki.contextgarden.net/Ubuntu#With_ConTeXt_Standalone_.E2.80.93_should_work_with_all_Ubuntu_versions

Font (OTF): https://www.google.com/fonts/specimen/Source+Sans+Pro

= MWE (test.tex) =
\definefont[VersionFont][name:sourcesanspro]

\starttext
  \VersionFont
  Hello, World
\stoptext
= EOF =

= LOG FILE (test.log) =
system  > callbacks > not registering frozen 'find_format_file'

open source > 1 > 1 >
/usr/local/context/tex/texmf-context/tex/context/base/cont-yes.mkiv

ConTeXt  ver: 2015.11.19 19:13 MKIV beta  fmt: 2015.12.2  int: english/english

system  > 'cont-new.mkiv' loaded
open source > 2 > 2 >
/usr/local/context/tex/texmf-context/tex/context/base/cont-new.mkiv
close source> 2 > 2 >
/usr/local/context/tex/texmf-context/tex/context/base/cont-new.mkiv
system  > files > jobname 'test', input './test', result 'test'
fonts   > latin modern fonts are not preloaded
languages   > language 'en' is active
open source > 2 > 3 > /tmp/test.tex
fonts   > preloading latin modern fonts (second stage)
fonts   > 'fallback modern-designsize rm 12pt' is loaded
fonts   > defining > source file 'SourceSansPro-Regular.ttf'
is not found
backend > xmp > using file
'/usr/local/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages   > flushing realpage 1, userpage 1
close source> 2 > 3 > /tmp/test.tex
close source> 1 > 3 >
/usr/local/context/tex/texmf-context/tex/context/base/cont-yes.mkiv

!LuaTeX error: cannot find OpenType font file for reading ()
 ==> Fatal error occurred, no output PDF file produced!
= EOF =

= MTXRUN =
$ mtxrun --script fonts --list -all sourcesanspro

sourcesanspro   sourcesansprosemiboldit
/usr/local/share/fonts/google/s/SourceSansPro-SemiboldItalic.ttf
= EOT =

I also noticed that there's a luatex-cache directory in $HOME, which
is strongly undesirable. (It should be $HOME/.luatex-cache, or reside
under /var/.)

Any ideas on why the font cannot be found? This was working until I
upgraded ConTeXt last night.

Thank you.
___
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
___

Re: [NTG-context] Upgrade to 2015.11.19 breaks OTF reader?

[Thangalin]

$ locate -i sourcesanspro
/home/.../luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tma
/home/.../luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/sourcesanspro-regular.tmc
/usr/local/share/fonts/google/s/SourceSansPro-Black.ttf
/usr/local/share/fonts/google/s/SourceSansPro-BlackItalic.ttf
/usr/local/share/fonts/google/s/SourceSansPro-Bold.ttf
/usr/local/share/fonts/google/s/SourceSansPro-BoldItalic.ttf
/usr/local/share/fonts/google/s/SourceSansPro-ExtraLight.ttf
/usr/local/share/fonts/google/s/SourceSansPro-ExtraLightItalic.ttf
/usr/local/share/fonts/google/s/SourceSansPro-Italic.ttf
/usr/local/share/fonts/google/s/SourceSansPro-Light.ttf
/usr/local/share/fonts/google/s/SourceSansPro-LightItalic.ttf
/usr/local/share/fonts/google/s/SourceSansPro-Regular.ttf
/usr/local/share/fonts/google/s/SourceSansPro-Semibold.ttf
/usr/local/share/fonts/google/s/SourceSansPro-SemiboldItalic.ttf

$ echo $OSFONTDIR
/home/.../.fonts:/usr/share/fonts:/usr/local/share/fonts:/usr/share/texmf/fonts/opentype:/usr/share/fonts/type1/gsfonts

The font is there, it's in the OSFONTDIR path.

Why isn't it found?

I've tried

   mtxrun --script fonts --reload

   luatools --generate

   context --reload

   context --generate

Further:

$ mtxrun --script fonts --list --all --pattern=sourcesans

sourcesanspro   sourcesansproregular
/usr/local/share/fonts/google/s/SourceSansPro-Regular.ttf
sourcesansproblack  sourcesansproblack
/usr/local/share/fonts/google/s/SourceSansPro-Black.ttf
sourcesansproblackitsourcesansproblackit
/usr/local/share/fonts/google/s/SourceSansPro-BlackItalic.ttf
sourcesansproblackitalicsourcesansproblackit
/usr/local/share/fonts/google/s/SourceSansPro-BlackItalic.ttf
sourcesansprobold   sourcesansprobold
/usr/local/share/fonts/google/s/SourceSansPro-Bold.ttf
sourcesansproboldit sourcesansproboldit
/usr/local/share/fonts/google/s/SourceSansPro-BoldItalic.ttf
sourcesansprobolditalic sourcesansproboldit
/usr/local/share/fonts/google/s/SourceSansPro-BoldItalic.ttf
sourcesansproextralight sourcesansproextralight
/usr/local/share/fonts/google/s/SourceSansPro-ExtraLight.ttf
sourcesansproextralightit   sourcesansproextralightit
/usr/local/share/fonts/google/s/SourceSansPro-ExtraLightItalic.ttf
sourcesansproextralightitalic   sourcesansproextralightit
/usr/local/share/fonts/google/s/SourceSansPro-ExtraLightItalic.ttf
sourcesansproit sourcesansproit
/usr/local/share/fonts/google/s/SourceSansPro-Italic.ttf
sourcesansproitalic sourcesansproit
/usr/local/share/fonts/google/s/SourceSansPro-Italic.ttf
sourcesansprolight  sourcesansprolight
/usr/local/share/fonts/google/s/SourceSansPro-Light.ttf
sourcesansprolightitsourcesansprolightit
/usr/local/share/fonts/google/s/SourceSansPro-LightItalic.ttf
sourcesansprolightitalicsourcesansprolightit
/usr/local/share/fonts/google/s/SourceSansPro-LightItalic.ttf
sourcesanspronormal sourcesansproregular
/usr/local/share/fonts/google/s/SourceSansPro-Regular.ttf
sourcesansproregularsourcesansproregular
/usr/local/share/fonts/google/s/SourceSansPro-Regular.ttf
sourcesansprosemibold   sourcesansprosemibold
/usr/local/share/fonts/google/s/SourceSansPro-Semibold.ttf
sourcesansprosemiboldit sourcesansprosemiboldit
/usr/local/share/fonts/google/s/SourceSansPro-SemiboldItalic.ttf
sourcesansprosemibolditalic sourcesansprosemiboldit
/usr/local/share/fonts/google/s/SourceSansPro-SemiboldItalic.ttf

Still not found.
___
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
___