Hi Ahhahh,
ahhahh <[email protected]> wrote on 10/01/2009 08:32:03 AM:
> The problem is I can't replicate the error, as the rendering is perfect
in
> every machine I have tested.
So I just looked at the release notes for 6u10. This is the
release they enabled the Direct3D rendering pipeline. That pipeline
is only used for Nvidia and ATI GPU's (not Intel). So you might
need a system with one of those to reproduce the problem. They also
seem to indicate that the card drivers must be up to date (which some
users may not be).
Additionally it indicates that you can disable the D3D pipe by
passing '-Dsun.java2d.d3d=false' when starting the JVM.
> I've been trying to find a way to get detailed Batik logs without
> recompiling the code with no success.
Batik was written before the various Java LOG API's were developed.
So it doesn't have an easy way to enable logging. Various modules have
'DEBUG' variables that can be manually set to true so it generates
additional System.out's.
> This is an example of one of my svg. I have reduced it by deleting most
of
> the lines and text.
> http://www.nabble.com/file/p25696843/D-1A-R00v05112801.svg
> D-1A-R00v05112801.svg
I now doubt the SVG content has much to do with the problem.
> I'm gonna try the ALWAYS_DYNAMIC hint. It may be a few days/weeks before
I
> get some feedback from my users, as they are reluctant to
install/reinstall
> JREs if not really necesary for their needs. Or maybe I'm 'lucky' and
find
> another problematic user soon. ;)
Hopefully the above info will help you reproduce and or get a better
work around to the issue. Good luck.
