·
> 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!
>
>
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
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
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
·
> 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
·
> 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.
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
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
·
> 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
> >
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
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.
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
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,
$ 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
14 matches
Mail list logo
