>>>>> "PB" == Peter Becker <[EMAIL PROTECTED]> writes:

PB> Thomas E Deweese wrote:
>> This bug should be fixed in the current CVS of Batik.

>>>>> "PB" == Peter Becker <[EMAIL PROTECTED]> writes:

PB> Currently I distribute my two patches (this one and the white
PB> edges problem) as class files with my program -- is this ok or
PB> should I use the CVS version? Will there be an 1.1 or 1.0.1
PB> release in the next time?

    Well, that decision is up to you.  I will point out that I believe
your publicly announced fix for the white edge problem, of subtracting
.5 instead of rounding is probably wrong, the one I committed does
nothing with .5 and just calls Math.round (originally the code added
.5 and then truncated to int, but this gives bad answers for negative
numbers, I then moved to Math.round, but missed to removing the .5
rounding factor).

    As to a 1.1 or 1.0.1 release this has been discussed however we
haven't set any planned dates for such a release.  My guess is that we
will have such a release, shortly before we start working on dynamic
support and/or modularization.  I wouldn't expect anything before the
end of the month.

PB> Is there a list/place to stay up to date with Batik problems
PB> without too much work? Bugzilla is quite complex and noisy, an
PB> announcement list would be cool ;-)

    Well, there is batik-dev which probably isn't much better, or
xml-batik-cvs which would allow you to see commit messages (not 100%
certain if that is the public name for it).  I'm not sure an
announcement list would cover this, since I don't think I would
necessarily post such a bug fix to an announcement list (which I
normally associate with 'big' announcements like version 1.0
released).

PB> While trying to use Bugzilla I found this:
PB> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1559

PB> It seems someone has a different opinion on how to handle PNGs --
PB> exactly the problem I feared to cause :-( Can you check this and
PB> add a comment? Maybe I really should open an account :-(

    This is actually the bug I 'fixed' (and forgot to close - since it
wasn't assigned to me).  I have now marked this bug as invalid and
provided a reason.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to