Cameron, Lewis,
thanks for your assistance.
Batik 1.6 would have been sufficient (but the update is nice, apparently
it adressed an issue I had with the distributed 1.6).
I wrote a test to find the problem, found it to be in my code not within
Batik: I was using the SVGDomImplementation instead of
SVG12DomImplementation when converting the tree from Dom4j to W3C dom,
hence the SVG 1.2 features were not available.
Thanks for pointing out that the regions are rendered, Cameron, you
saved me from wondering why I got a black blob instead of flowtext.
I hope I can include everything into my working code as easily as I
could create the test.
Bye
-Urs
Lewis Keen wrote:
Urs,
The version of Batik I am using was a nightly build taken on the 29th
of April 2006. I found this one slightly more stable in certain things
I was using (don't ask me how, I'm not quite sure :)).
It may be worth just getting the latest nightly build and seeing how it
goes.
Regards,
Lewis
On 5/19/06, Urs Reupke <[EMAIL PROTECTED]> wrote:
Hi Cameron,
thanks for clarifying the need for the version attribute.
You wrote:
> Perhaps you're not using a recent enough version of Batik?
Which version would qualify as "recent enough"? Currently, I am using
the 1.6 release available from the website "as is".
There are several SVG12* classes present in the archives, most of them
defining constants. Do I need to specify anthing more for Batik to
operate with SVG 1.2?
Regards
-Urs
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
