From: Philipp Gesang <phg@phi-gamma.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Upgrade to 2015.11.19 breaks OTF reader?
Date: Tue, 8 Dec 2015 01:22:43 +0100 [thread overview]
Message-ID: <20151208002243.GA13071@phlegethon> (raw)
In-Reply-To: <5664AC40.9090708@wxs.nl>
[-- Attachment #1.1.1: Type: text/plain, Size: 1030 bytes --]
···<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
[-- Attachment #1.1.2: font-otr.lua-fix-resources.filename.patch --]
[-- Type: text/x-diff, Size: 545 bytes --]
--- 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.features or { }, -- we need to add these in the loader
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-12-08 0:22 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 [this message]
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=20151208002243.GA13071@phlegethon \
--to=phg@phi-gamma.net \
--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).