Juergen Kreileder wrote:
The problem is that the URW fonts are available with two different
> foundries: urw and abode. The two foundries use different family
> names for the fonts too. The reason why we currently use the urw
> foundry is that the abode foundry uses ambiguous family names, this
> may result in using the symbol fonts from {75,100}dpi instead of the
> symbol font from urw, this gives a bad font display.
In the font set that I downloaded from the gimp site, the family names are
the same between the "adobe" and "urw" foundary. In particular, in both
cases, it is "Zapf Dingbats" and "Symbol". So perhaps, the names were
changed as part of making the Debian distribution.
> Also, it's advisable to make the fonts available through the Xserver
> directly (i.e. do not use a font server for the urw fonts). This
> allows the JDK to get direct access to the font files.
So are you saying that in my XF86Config file, I should have the actual
directory for the URW fonts in addition to the line which specifies the font
server (and remove them from the configuration file for the font server)? Or
would it be better to put all of the JDK fonts together in the
"jre/lib/fonts" directory? Is this directory always checked first? How does
the JDK behave differently when you make the fonts available through the font
server? I do not see the "dingbats" errors anymore.
Thanks for your input and also the various font files.
Cynthia Jeness
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
