This is related to the other issue someone on the list brought up, where auto-detect should be able to stop once it finds it, should be able to search the classpath first, search the jars first, not search fonts installed at all with either the Java or the OS...
If we're able to get it to use a font just by adding it to a jar on the classpath but we have to use the auto-detect and it's going to waste time searching every font installed then yes it's not worth it, I'll stick with hardcoding a path on the server and pulling in that file as I am now. -----Original Message----- From: Tor-Einar Jarnbjo [mailto:[email protected]] Sent: Friday, October 29, 2010 3:50 PM To: [email protected] Subject: Re: Eclipse project with ant to build "fonts.jar" Am 29.10.2010 17:26, schrieb Eric Douglas: > This sounds awesome. I run fop in client/server through webstart. > Hi Eric, be aware though that FOP need to write a font cache to disk if it's not acceptable for you to spend quite some time analyzing the available fonts every time you run it. Enabling the auto-detect feature (as Wim suggested) would also cause your client to search the system font directory for fonts, which may cause an incorrect font to be selected if a font with the same name is installed locally. Both issues would also require your WebStart client disk access privileges on the client. Regards, Tor --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
