[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-fonts-devel] Fonts from package misbehave in exported PDF

Am 15.09.2012 07:05, schrieb Norbert Preining:
We are currently shipping the type1 fonts with family names without
strings in the fonts.scale file (/etc/X11/fonts/Type1/tex-gyre.scale)

s/strings/spaces/ ?

Now I am not convinced what we actually should do:
1* drop type1 fonts completely from X support and only ship OTF fonts

That's too much of a loss and gains nothing in return.

2* keep type1 fonts shipped, but change names to match TeX Gyre Chorus etc

That's an incompatible deviation from upstream, who apparently chose the different names (i.e. once with spaces and once without) on purpose, c.f. <http://www.gust.org.pl/projects/e-foundry/tex-gyre/nfp11.pdf> slides 12 and 13 and also the other documents on the bottom of their homepage.

3* only add your fontconfig file and keep the type 1 fonts as they are

That's my obvious choice. Please note that the presence/absence of the spaces in the font names does not play a role in fontconfig's matching rules.

Without my fontconfig file:
$ fc-match texgyreheros
qhvr.pfb: "TeXGyreHeros" "Regular"
$ fc-match "tex gyre heros"
qhvr.pfb: "TeXGyreHeros" "Regular"

With my fontconfig file:
$ fc-match texgyreheros
texgyreheros-regular.otf: "TeX Gyre Heros" "Regular"
$ fc-match "tex gyre heros"
texgyreheros-regular.otf: "TeX Gyre Heros" "Regular"

Is there a way to tell fontconfig to reject all TeX Gyre fonts
with format Type 1 without listing *every font*

I did not find a way. You can reject them based on file names, but I found rejecting "/usr/share/fonts/X11/Type1/q*.pfb" rather fragile.

 - Fabian

Reply to: