From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Upgrade to 2015.11.19 breaks OTF reader?
Date: Thu, 3 Dec 2015 22:29:43 +0100 [thread overview]
Message-ID: <5660B447.6080805@wxs.nl> (raw)
In-Reply-To: <20151203173919.GA17901@phlegethon>
On 12/3/2015 6:39 PM, Philipp Gesang wrote:
> ···<date: 2015-12-03, Thursday>···<from: Hans Hagen>···
>
>> On 12/3/2015 8:27 AM, Philipp Gesang wrote:
>>> ···<date: 2015-12-02, Wednesday>···<from: Thangalin>···
>>> 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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-12-03 21:29 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 [this message]
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
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=5660B447.6080805@wxs.nl \
--to=pragma@wxs.nl \
--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).