What an interesting question. Five minutes of investigation suggests
that the JVM is disinclined to drill down into the directory structure
under /usr/share/fonts in order to find fonts in, say,
/usr/share/fonts/truetype/windowsrips. If I symlink
/usr/share/fonts/truetype/windowsrips then I get the fonts in that
directory, but not in /usr/share/fonts/truetype/freefont; and of course
I've then got to copy the lucida fonts that came with the JVM to
windowsrips if I want to go on using them.
A better solution would seem to be to symlink to the font files
themselves from the lib/fonts directory. So in my case:
ln -s /usr/share/fonts/truetype/freefont/Junicode-Regular.ttf
and so on. The big benefit is that when I upgrade the font to the next
version I don't have to copy it both to the system directory and the JVM
Thanks for bringing this up and getting me to think about it.
(more communicative than usual when the alternative is grading papers)
James Cummings wrote:
> Peter Baker wrote:
>> I should add that this ought to work under any operating system. To
>> make any font visible to the Java Virtual Machine, just copy it into
>> the lib/fonts (lib\fonts, whatever) directory of your Java
>> installation and then restart any Java apps you have going. The font
>> should show up in the fonts menu of any app that gives you a choice
>> of fonts.
> Does this work if you symlink /usr/lib/j2sdk1.5-sun/jre/lib/fonts to
> /usr/share/fonts ?
> Dr James Cummings, Oxford Text Archive, University of Oxford
> James dot Cummings at oucs dot ox dot ac dot uk