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

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : [email protected] / 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
___________________________________________________________________________________

Reply via email to