[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/50152: fontconfig and tex fonts
The following reply was made to PR bin/50152; it has been noted by GNATS.
From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
Cc: gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/50152: fontconfig and tex fonts
Date: Tue, 18 Aug 2015 19:10:10 +0200
On Tue, Aug 18, 2015 at 09:05:00AM +0000, dholland%netbsd.org@localhost wrote:
> I noticed today that fontconfig is not configured to look at tex fonts
> in /usr/pkg/share/texmf-dist/fonts. So I tried adding it. In addition
> to ostensibly failing (or spewing unhelpful warnings given -v) this
> produced results where, in addition to a bunch of useful fonts
> previously not accessible, it now offers several thousand fonts with
> useless tex names like "grxi1095".
So barely any information, hard to figure things out...
> It's enough fonts that inkscape took minutes to load them all, but
> that may be inkscape's fault.
Jared suggested a missing fc-cache invocation?
> This is not a suitable state of affairs:
> 1. The useful fonts (provided one has them installed via tex,
> obviously) should be configured by default.
This isn't a base system issue.
> 2. It shouldn't fail or spew warnings. (Even before I started
> mucking about, I was getting warnings/failures from
> /usr/X11R7/lib/X11/fonts/encodings, which is a normal part of an
> X11 font tree that it doesn't seem to know what to do with.
Well, nothing we can do here without knowing what it actually printed.
> 3. It should know how to map the useless tex font names (most of
> which I believe are variations of a much smaller number of real
> fonts) to real font names.
This is not a bug in fontconfig. The Type1 fonts like e.g. grxi1095
clearly have bogus family names. It is not the job of fontconfig to be
an oracle and second guess the meta data of the fonts.
Main Index |
Thread Index |