|
|
On Fri, Dec 22, 2006 at 10:13 +0100, Norbert Preining wrote:
> In fact it is much more funny than this, because all expert fonts are
> completely messed up.
>
> I suspect that this is NOT a fontconfig problem, but a user app problem,
> as the do not evaluate ALL properties returned by the fontconfig
> library. I had a long discussion on this with the OOo guys, see here:
> http://qa.openoffice.org/issues/show_bug.cgi?id=42835
> where examples for fonts, and weird things are described (including
> screenshots).
I am not sure if this an issue of fontconfig, the client app or the
font, but I do suspect fontconfig. And even if it were the client app,
then reference implementations like fc-match show the same problem.
Currently I get
~$ fc-match LMRoman10
lmdunh10.pfb: "LMRoman10" "Dunhill"
But as we have seen before, this varies sometimes.
BTW, I have tried the snippet for ~/.fonts.conf provided by Anthony. The
consequence was like this:
~$ fc-match LMRoman10
lmr10.pfb: "LMRoman10" "Regular"
~$ fc-match LMRoman10:Bold
lmr10.pfb: "LMRoman10" "Regular"
~$ fc-match LMRoman10:Italic
lmr10.pfb: "LMRoman10" "Regular"
Now all the bold or italic variants were no longer accessible. However,
I like the idea of adding additional information to aid fontconfig when
matching fonts in large families.
Dear fontconfig maintainers: Is there a way to add information like
'which font should be the default font'? This would really be helpful.
cheerio
ralf
--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
|
|