David Eppstein wrote:
In article <[EMAIL PROTECTED]>, Andreas Neumann <[EMAIL PROTECTED]> wrote:
I read your thread (july 2003) on the Batik Mailinglist on trying to get Squiggle running under MacOSX10.2.6. I ran into exactly the same problem?
I read that the installed fonts could be the problem?
This is our current suspicion, as the simple test application we put togeather (just gets the list of fonts) failed on these systems.
Have you figured out which fonts could cause the problem?
As far as I know no one has tried to identify at least one font that causes the problem.
I have essentially the same configuration, and don't get that problem, but I do get a bunch of annoying error messages whenever I start up squiggle (or use batik-rasterizer on an SVG containing text):
This is also why we conclude it has to do whith what fonts are installed.
Also note the times -- Java is taking a very long time looking at fonts that have no relevance to the current job. Presumably this is mostly an Apple-Java problem rather than a Batik problem, but is there any way Batik could get Java to only look at the fonts it wants, instead of all of them?
Unfortunately no, CSS has rather complex rules on how to match font names, this forces us to get the entire list of available fonts and canonicalize it so that we can match the string the user provides. For example 'timesnewroman' must match the installed font 'Times New Roman'.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
