Juergen Kreileder wrote:
>
> >>>>> Nathan Meyers writes:
>
> Nathan> Paolo Ciccone wrote:
> >>
> >> On Tue, Dec 21, 1999 at 11:22:03PM +0100, Juergen Kreileder wrote:
> >> > No big surprise, they've commented out the relevant entries in the
> >> > font.properties file. I'll do the same for the next Blackdown release
> >> > as people think that it is a bug, but it isn't.
> >> >
> >> > Try to display dingbats characters (0x2701 - 0x27be) on an AWT
> >> > component with the Inprise JDK, you'll get no warnings but the
> >> > component only will show question marks: '????'. The warnings from
> >> > the Blackdown JDK just tell you immediately that something might not
> >> > work correctly.
> >>
> >> Does anybody know if installing the URW fonts fixes the problem
> >> ? If yes, than it could be a requirement for the JDk and it
> >> just could be mentioned in the README.
>
> Nathan> Yes, if the font.properties file is changed accordingly
> Nathan> and the fonts are made available in one of two possible
> Nathan> ways:
>
> Nathan> 1) Added to the X server's font path.
>
> Nathan> 2) Added to the AWT's font path with the JAVA_FONTS environment
> Nathan> variable.
>
> Nathan> The advantage of the latter approach is that font
> Nathan> rendering is performed by the AWT instead of X, and the
>
> RC3 should do that in case 1 too.
>
> Nathan> Graphics2D manipulations work. If you use JAVA_FONTS, you
> Nathan> need to specify a path containing all directories from
> Nathan> with the AWT gets scalable fonts, including the directory
> Nathan> containing the default fonts shipped with the JDK.
>
> Juergen
>
> --
> Juergen Kreileder, Blackdown Java-Linux Team
> http://www.blackdown.org/java-linux.html
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I tried to get this to work with blackdown jdk1.2.2-RC3. I already
had URW fonts. Some of the documentation seemed to point towards
installing Microsoft truetype fonts, as well. Since I am running
RH6.0, which has the xfs font server, I did that.
I edited the config file for xfs so that it contains the
path of the URW fonts and the truetype fonts, as well as all of
the usual fonts in the XF86 configuration. The repetitive warnings
about missing dingbat fonts did not, unfortunately, go away.
I would bet that a lot of the developers using linux/jdk are running
RH6.x. It would be very useful if someone who really understands
this font problem could document a solution to this problem, which
does not involve removing dingbat fonts, or any other fonts for
that matter, from availability. It seems that commenting entries
out of font.properties will at some point cause cross-platform
incompatibilities.
-- Alan
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
