Glen Mazza wrote:
1.) Please go ahead and commit the code on your side
right now--Gump will complain for the next couple of
days before the change is made on our side, however.
But it's easiest for me to code against something
already made.
This is done. The commit includes a couple of other
I wish I could--production is a complete mess to work
with! But what about Gump? It will be complaining
each and every day about fop-maintenance (although it
won't care about fop-development once we update *it*.)
Gump wants compliance with the latest library
versions--this is the problem Jeremia
Glen Mazza wrote:
next few days to fix the transcoders--on 0.20.x
production
Skip this, it's not worth. We should finally concentrate
on HEAD.
J.PIetschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, emai
--- Thomas DeWeese <[EMAIL PROTECTED]> wrote:
>
> Thanks, there isn't a huge rush but I wanted to
> make
> sure this wasn't a really bad time for you.
>
It's always a bad time! ;)
1.) Please go ahead and commit the code on your side
right now--Gump will complain for the next couple of
day
Thomas,
Sorry for the delay in response--failing a answer from
the other FOP committers--I'll look into the issue
this weekend.
In the meantime, as you say, the pdf transcoder needs
updating--can you send us the patch where Batik
changed (or the ViewCVS link if it was already done),
also to anoth
