Hi Cameron
Cameron McCormack wrote:
Getting back on to this…
Cameron McCormack:
Cool. It does fix the batik70.svg rendering under OS X. Unfortunately
it didn’t seem to help the other rendering issues.
All of the rendering issues under OS X also existed with Batik 1.6.
Since they’re not regressions, I suggest we leave them for now and forge
ahead with the 1.7 release.
Still waiting on Rhino to have a new release (I believe Atilla is
working on better security policy work in general, rather than applying
the workaround I supplied). What does everyone think of making the
release candidate with Rhino 1.6R5 + a patch to make the debugger work,
and then making the final 1.7 release once Rhino’s next distribution is
out?
Sounds good to me. I use the svn version for the moment,
as I need some new features added since 1.6.
I think it would be wise to wait 'till the security
issues in Rhino are fixed and then release a new Batik package.
You can then say, ok people use 1.7, it has all the new features and
it doesn't have any *major* bugs/security issues. If you release 1.7
without fixed Rhino, you'll need to do a 1.75 or 1.8 shortly after,
and that's not what you want.
Greetings from Luxembourg,
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
