On Sep 28, 2004, at 2:08 AM, Chris Bowditch wrote:
Simon Pepping wrote:
I do not know if this is a lot of work or not. To me it seems a
lot. Perhaps you may argue that this is not required for a 0.3
release. But to me it is rather essential to the new design. Without
it we might as well remain
identified of making layout
easier to work on.
I do not know if this is a lot of work or not. To me it seems a
lot. Perhaps you may argue that this is not required for a 0.3
release. But to me it is rather essential to the new design. Without
it we might as well remain with the maintenance lay
ue that this is not required for a 0.3
release. But to me it is rather essential to the new design. Without
it we might as well remain with the maintenance layout system.
I understand that the new design for renderers has been more
successful, and may be a reason to want a release of the developmen
Chris,
thank you doing this. I think it's important to have a good instrument
to determine our progress towards an initial release. I was a bit
shocked when I summed up only the points you've marked as high priority:
20 weeks. It got me thinking and running all the example files ag
Team,
I have been trying to work out what is left to do be done before we can do an
initial release of HEAD, 0.3, say. I know some of you will prefer to aim for a
1.0 and get everything right first time, but please bear with me.
I have consolidated the layout issues from [1] and [2] The
Chris, Jeremias, and anyone else looking at FOray code:
I have created the following branch in FOray's CVS that you will want to use
for your evaluation:
rel_0_1_branch
I have started some other changes in the root that should probably be
evaluated separately.
I apologize for the inconve
Jeremias Maerki wrote:
> I'm simply thinking that adding statics is a lot easier than
> removing them again. I usually create non-static classes and
> create singletons around them if necessary or convenient.
> That's basically it.
>
> > One of the main purposes of
> > FontServer was to share
Sorry for the delay.
On 16.07.2004 19:00:25 Victor Mote wrote:
> Jeremias Maerki wrote:
>
> > Making these parts into separate components is in line with
> > what I have in mind when can talk about a shared repository
> > between Batik and FOP. I hope I can take a good look into
>
> Good. I t
Jeremias Maerki wrote:
> Making these parts into separate components is in line with
> what I have in mind when can talk about a shared repository
> between Batik and FOP. I hope I can take a good look into
Good. I think it has potential to be useful to many applications.
> what you did later
re much more
cleanly solved.
When the XML Graphics project is set up I hope we can soon talk about
the details of my ideas. I'd love to have you with us to work on the
shared components.
On 13.07.2004 22:40:43 Victor Mote wrote:
> FOP Devs:
>
> I am pleased to announce the release of
Victor Mote wrote:
FOP Devs:
I am pleased to announce the release of FOray 0.1 alpha 1. This release is
only useful to FOP developers. Some useful information about the release can
be found in these places:
http://foray.sourceforge.net/module/font/index.html
http://foray.sourceforge.net/module
FOP Devs:
I am pleased to announce the release of FOray 0.1 alpha 1. This release is
only useful to FOP developers. Some useful information about the release can
be found in these places:
http://foray.sourceforge.net/module/font/index.html
http://foray.sourceforge.net/module/font/release.html
Clay Leeds wrote:
Thanks for the respectful response. I'm aware that HEAD release is
adversely affected by MAINTENANCE work (hence the "I don't want to start
a ware here, but..." :-)), however, I posted this for a few of reasons:
1) fop-dev team might discuss this in ligh
On Jan 7, 2004, at 12:07 PM, J.Pietschmann wrote:
It works for me for generating PDF for quite some time. I get NPE when
reloading a FO source in the AWT appilcation, but this maz have other
reasons, I didn't try to track it down.
As long as I can remember I got NPE when clicking the [Reload] butto
Chris Bowditch wrote:
Okay, but you said yourself that the adjustments you made to tables has
probably broken some other things, so we would need to go through a RC,
and bug fix cycle.
It works for me for generating PDF for quite some time. I get NPE when
reloading a FO source in the AWT appilcat
> -Original Message-
> From: Chris Bowditch [mailto:[EMAIL PROTECTED]
>
>
> I understand the desire to add new features like the Tif generator into
> the maintenance code. However, doing so would mean effort is distracted
> away from HEAD development. The sooner we
Postscript=>TIF via GhostScript). It works but is clunky. Since it
works, this isn't a make-or-break for me, but is more of a "would be
nice"...
I understand the desire to add new features like the Tif generator
into the maintenance code. However, doing so would mean effort is
t is clunky. Since it works, this isn't a
make-or-break for me, but is more of a "would be nice"...
I understand the desire to add new features like the Tif generator into
the maintenance code. However, doing so would mean effort is distracted
away from HEAD development. The sooner
t;.
Web Maestro Clay
On Jan 7, 2004, at 12:42 AM, Chris Bowditch wrote:
J.Pietschmann wrote:
Well, we could release the current CVS as 0.20.5.1. The table memory
fix is probably important to many users. THere is a slo a minor fix
concerning leader expansion there.
Okay, but you said yourself that t
J.Pietschmann wrote:
Well, we could release the current CVS as 0.20.5.1. The table memory
fix is probably important to many users. THere is a slo a minor fix
concerning leader expansion there.
Okay, but you said yourself that the adjustments you made to tables has
probably broken some other
Chris Bowditch wrote:
Thus, I just wanted to know if some sort of 0.20.6 release will be
upcoming in the future
No, no further releases are planned from the maintenance branch, and all
development is focused on CVS Head.
Well, we could release the current CVS as 0.20.5.1. The table memory
fix is
> --- Thomas DeWeese <[EMAIL PROTECTED]> wrote:
> >
> > At least one of the issues is with the
> > PDFGraphics2D.
> > in PDFGraphics2D.java:632 in draw(shape s). There
> > is
> > a check for a newTransform which inexplicably
> > decides that
> > if the new transform is the Identity transform t
--- Thomas DeWeese <[EMAIL PROTECTED]> wrote:
>
> At least one of the issues is with the
> PDFGraphics2D.
> in PDFGraphics2D.java:632 in draw(shape s). There
> is
> a check for a newTransform which inexplicably
> decides that
> if the new transform is the Identity transform there
> is
> no cha
> -Original Message-
> From: Glen Mazza [mailto:[EMAIL PROTECTED]
> Also, providing a link to the bug is indicated
> here--asking Thomas to hunt through Bugzilla in order
> to help us out--these problems are with our code, not
> his--is somewhat rude.
>
Ok. I probably supposed that Thomas
Glen Mazza wrote:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23883
Thomas,
You needn't bother on this at this time--we have yet
to find where Batik is wrong. So far, Squiggle has
drawn the SVG correct *all* the time. But comments
always welcome, and it's good for you to be aware of
the
Good--I was concerned that this was just me having the
problem.
Glen
--- "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
> Glen Mazza wrote:
> > I'll leave the 0.20.x branch alone until others
> > complain about this problem, however.
>
> There is no problem in the maintenance branch,
> because it wa
--- "Andreas L. Delmelle" <[EMAIL PROTECTED]>
wrote:
>
> Thomas,
>
> Can you perhaps have a look at bug 23883? In
> embedded SVG, something's going
> wrong with translate() when large numbers are used.
> Apparently this works
> fine for svg:text elements, but a polyline gets
> drawn really ugly...
> -Original Message-
> From: Glen Mazza [mailto:[EMAIL PROTECTED]
>
> Thanks, Tom, for your quick assistance. I didn't know
> about the AWT threading issue you brought up.
>
Thomas,
Can you perhaps have a look at bug 23883? In embedded SVG, something's going
wrong with translate() when l
Glen Mazza wrote:
I'll leave the 0.20.x branch alone until others
complain about this problem, however.
There is no problem in the maintenance branch, because it was
fixed there (and unfixed, and refixed etc...) ages ago.
J.Pietschmann
Thanks, Tom, for your quick assistance. I didn't know
about the AWT threading issue you brought up.
I went ahead and added explicit System.exit() commands
to Fop.java in 1.0. I was somewhat reluctant about
this though because others haven't been complaining
about this problem, and for some rea
Thanks, Tom, for your quick assistance. I didn't know
about the AWT threading issue you brought up.
I went ahead and added explicit System.exit() commands
to Fop.java in 1.0. I was somewhat reluctant about
this though because others haven't been complaining
about this problem, and for some rea
gh). I'm concerned others may be
getting this hanging thread problem on their machines.
Results of the below FO (work computer):
0.20.5 release: works fine (1-yr. old Batik)
0.20.x nightly: hangs (Batik updated one month ago,
due to API changes)
1.0 dev: hangs (Batik version of two
puter):
0.20.5 release: works fine (1-yr. old Batik)
0.20.x nightly: hangs (Batik updated one month ago,
due to API changes)
1.0 dev: hangs (Batik version of two weeks
ago,
also with nightly build)
All three still generate a correct PDF document w/SVG,
even though the app hangs (I just ne
Thomas Sporbeck wrote:
It might be a fundamental decision if FOP is a kind of "toolbox" for
developers or if it should be an "out of the box-product" for nearly everyone
It is Open Source. If you find issues and create patches, send
them in. Every contribution is welcome.
J.Pietschmann
everything
else. It will certainly require some amount of testing, which
means another release candidate and which is therefore quite
unpopular with our release manager.
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
I might be wrong, but I think most users of FOP are using it
server-side, where resources (especially memory) are more readily
available. This might explain your problems, I think little energy has
been spent to optimize FOP's memory requirements.
Yes, I agree. B
On Tue, 2003-07-08 at 14:31, Bertrand Delacretaz wrote:
> I might be wrong, but I think most users of FOP are using it
> server-side, where resources (especially memory) are more readily
I don't know about most users, but I am using FOP client-side since I do
not have a server.
Felix
Le Mardi, 8 juil 2003, à 10:14 Europe/Zurich, Thomas Sporbeck a écrit :
...It might be a fundamental decision if FOP is a kind of "toolbox"
for developers or if it should be an "out of the box-product" for
nearly everyone - I think there's so much good ideas in it that
everyone should be able to
rogrammers implement the same feature separately).
The current pre-release needs about 1 MB RAM per page in our reports - that is indeed
no problem if you have a machine with about 256 MB or more and have no other
applications loaded while using FOP.
But we're using FOP as add-on to some of our appli
PM
To: [EMAIL PROTECTED]
Subject: RE: 0.20.5 release
I would agree to Ricardo. We're using tables for inventory lists
containing about 500 pages. The memory situation in that reports is
really critical and we cannot force the users to set filters.
On the other hand: to us it doesn't matter if t
rsday, June 19, 2003 3:41 PM
To: [EMAIL PROTECTED]
Subject: RE: 0.20.5 release
I would agree to Ricardo. We're using tables for inventory lists
containing about 500 pages. The memory situation in that reports is
really critical and we cannot force the users to set filters.
On the other hand
I would agree to Ricardo. We're using tables for inventory lists
containing about 500 pages. The memory situation in that reports is
really critical and we cannot force the users to set filters.
On the other hand: to us it doesn't matter if this enhancement comes
with 0.20.5 or with a later version
here is also an older one for version
0.20.3). It would be nice if one of you guys could take a look at those
patches and consider them before issuing the final 0.20.5 release.
Congratulations to you all on an excellent job, you are doing,
Ricardo Amador
-Original Message-
From: Christian
Christian Geisert wrote:
RC3a seems to be rather stable and the changes since then look
non-critical to me. What about doing the release now (read: next days)
(and maybe 0.20.5a later if we get more hyphenation patterns back)
Or should we make the changes proposed by Jörg (improved memory
usage
On 17.06.2003 19:16:23 Christian Geisert wrote:
> RC3a seems to be rather stable and the changes since then look
> non-critical to me. What about doing the release now (read: next days)
+1
> (and maybe 0.20.5a later if we get more hyphenation patterns back)
Don't count on t
Ok,
RC3a seems to be rather stable and the changes since then look
non-critical to me. What about doing the release now (read: next days)
(and maybe 0.20.5a later if we get more hyphenation patterns back)
Or should we make the changes proposed by Jörg (improved memory
usage with tables - see
At 09:08 AM 2/18/2003, you wrote:
the second Release Candidate for 0.20.5 is finally available at
http://www.apache.org/dist/xml/fop for downloading and testing.
(New download location - please use a mirror if possible)
Cheers, and congratulations all around.
This was a bumpy one (especially
Hi all,
the second Release Candidate for 0.20.5 is finally available at
http://www.apache.org/dist/xml/fop for downloading and testing.
(New download location - please use a mirror if possible)
It is planed to make the actual release on on february the 28th
if no serious bugs show up.
The
Ok, I worked on the patch. Some notes:
Mark C. Allman wrote:
These files just have a "mayContainMarker()" method added:
I don't understand the advantage of this. Checks for
proper FO structure are flaky anyway. You also canned
the check that a marker can be preceded by whitespace.
This is actua
Christian Geisert wrote:
> So I propose the following plan:
> Make another RC on february 17th and do the final 0.20.5 release
> on february the 28th (no delay except for very valid reasons)
>
> Comments?
+1
Victor Mote
-
Christer,
Christer Sandberg wrote:
This is our SVG width and height:
Up to this point, I have no experience with SVG, but I was surprised to
see that there is no unit of measurement (cm, mm, pt, px) in the height
& width.
When I added some println() statements to PDFRenderer, both in 0.20.1
Christian Geisert wrote:
Ok,
in a perfect world the 0.20.5 release would have happend last
year and we all were working on HEAD now but in reality we're
still fixing bugs (which is ok as it will take some time till
the first "redesign-relase") but nevertheless we should finally
fi
Christian Geisert wrote:
in a perfect world the 0.20.5 release would have happend last
year and we all were working on HEAD now but in reality we're
still fixing bugs (which is ok as it will take some time till
the first "redesign-relase") but nevertheless we should finally
fini
c on this bug report
and wouldn't it be nice to dig in to this before the final release.
Take a look at line 526 of PDFRenderer.java, it clips to the size of the SVG image.
Is it possible that part of the SVG goes outside the SVG width and height?
Try commenting it out or changing the siz
+1, but strict bugfixing only, or else we're never going to make it.
On 12.02.2003 17:44:14 Christian Geisert wrote:
> Ok,
>
> in a perfect world the 0.20.5 release would have happend last
> year and we all were working on HEAD now but in reality we're
> still fixing bug
tivity in this list etc on this bug report
> and wouldn't it be nice to dig in to this before the final release.
Take a look at line 526 of PDFRenderer.java, it clips to the size of the SVG image.
Is it possible that part of the SVG goes outside the SVG width and height?
Try commenting it out
Christian Geisert wrote:
Ok,
in a perfect world the 0.20.5 release would have happend last
year and we all were working on HEAD now but in reality we're
still fixing bugs (which is ok as it will take some time till
the first "redesign-relase") but nevertheless we should finally
fi
Christian Geisert wrote:
So I propose the following plan:
Make another RC on february 17th and do the final 0.20.5 release
on february the 28th (no delay except for very valid reasons)
+1
J.Pietschmann
-
To unsubscribe, e
Christian Geisert wrote:
Ok,
in a perfect world the 0.20.5 release would have happend last
year and we all were working on HEAD now but in reality we're
still fixing bugs (which is ok as it will take some time till
the first "redesign-relase") but nevertheless we should finally
fi
Ok,
in a perfect world the 0.20.5 release would have happend last
year and we all were working on HEAD now but in reality we're
still fixing bugs (which is ok as it will take some time till
the first "redesign-relase") but nevertheless we should finally
finish 0.20.5.
So I propos
Hello,
FOA (Formatting Object Authoring tool)
http://foa.sourceforge.net
has a new release: 0.5.0.
The new features for this release are:
- New Bricks:
- Block and Inline Containers
- Footnotes
- Floats
- External (Foreign) Objects
- Leaders
- New Support:
- Table Caption
J.Pietschmann wrote:
Christian Geisert wrote:
Thanks for contribution but as I'm planing to do the 0.20.5 release
tomorrow (really ;-) it's just to late for it.
I want to take a closer look at this:
Ok?
1. We need to keep a list of all pages. If a marker is refer
ting rid of that also.
-- Mark C. Allman
-- Allman Professional Consulting, Inc.
-- www.allmanpc.com, 617-947-4263
-Original Message-
From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 06, 2003 8:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Changes to maintenance release
Christian Geisert wrote:
Thanks for contribution but as I'm planing to do the 0.20.5 release
tomorrow (really ;-) it's just to late for it.
I want to take a closer look at this:
1. We need to keep a list of all pages. If a marker is referenced on a
later page we need to be able t
Mark C. Allman wrote:
Attached is the cvs diff for all 22 files changed. Also attached (in
[..]
Comments, criticisms, and feedback are encouraged.
Thanks for contribution but as I'm planing to do the 0.20.5 release
tomorrow (really ;-) it's just to late for it.
[Sorry to re-post this. I first had all files as
attachments—too large (109k > 100k). Then I put the test stuff
into a zip file, but this exceeded the fop-devel list max size (59k >
50k). So all are now in the zip file.]
Attached is the “cvs diff” for all 22 files
changed. Also atta
Attached is the “cvs diff” for all 22 files
changed. Also attached (in the zip file) is a test XSLFO file (mca.fo)
and a pdf output run with my modified code. The test files are in a zip
file since they’d be too large (together) to send (mailer-daemon limits
to 100k).
Notes on the
Christian Geisert wrote:
I managed to workaround bug #15936 with making all InlineSpaces non
resizable if a LineArea contains a leader. This renders leader.fo a bit
different (but IMHO barely recognizable).
This is dangerous, because it overflows the line. Actually,
the page number is supposed
t this, if not I will commit it
and do the release.
Christian
? lib/jimi-1.0.jar
Index: src/org/apache/fop/layout/LineArea.java
===
RCS file: /home/cvspublic/xml-fop/src/org/apache/fop/layout/Attic/LineArea.java,v
retrieving revision
Title: RE: Release
Hi,
Firstly apologies for the HTML attached to the end of this message, I think it's something to do with the mail server which I don't have access to. I have asked about it, but I'm going on holiday tomorrow, and haven't got a reply yet.
Some thou
Christian Geisert wrote:
Joerg has mentioned bug #15936 as showstopper to me.
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15936)
Actually, I can't reproduce it right now. I'll give it
another try tomorrow.
J.Pietschmann
-
On 20.01.2003 16:33:28 Christian Geisert wrote:
> Ok,
>
> we should finally finish 0.20.5
>
> Open issues:
> Remove xml-apis from Batik (Jeremias?)
done (in branch).
> Joerg has mentioned bug #15936 as showstopper to me.
> (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15936)
>
> Should w
Ok,
we should finally finish 0.20.5
Open issues:
Remove xml-apis from Batik (Jeremias?)
Joerg has mentioned bug #15936 as showstopper to me.
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15936)
Should we try to fix this? If yes any volunteer?
Anything else?
Christian
-
Uh, yeah. Almost forgot. I guess I can come up with a first version
until Thursday.
On 09.01.2003 19:42:31 Christian Geisert wrote:
> Jeremias Maerki wrote:
>
> [..]
>
> > Christian, when do you plan to release 0.20.5? Seems like no major bugs
> > are around, right?
&g
Guillaume Déflache wrote:
Christian Geisert wrote:
- Perfo[r]mance tuning
Typo in CHANGES: bug number should read 14013, not 14103 (Cocoon bug)!
Fixed, thanks.
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For add
Christian Geisert wrote:
- Perfo[r]mance tuning
Typo in CHANGES: bug number should read 14013, not 14103 (Cocoon bug)!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Hi all,
the Release Candidate for 0.20.5 is finally available at
http://xml.apache.org/dist/fop for downloading and testing.
It is planed to make the actual release in about two weeks
if no serious bugs show up.
Changes since 0.20.4 include:
- Fixed link hotspot positioning
- Fixed multi
Hi all,
I've (finally) updated the build process to the new Forrest docs
and I'm ready now for doing the Release Candidate.
If this is ok for everybody I'll do it later today.
Christian
-
To unsubscribe,
Jeremias Maerki wrote:
How will we maintain the website after the copy? Change in trunk then
copy over to maint branch each time something is changed? Or can we
Yes, I'm not sure if automatic merging would work and I don't think
there will be a lot of changes.
Christian
Peter B. West wrote:
> Victor Mote wrote:
> > Christian Geisert wrote:
> >
> >
> >>for the documentation for the maintenance release I think the
> >>best thing is to copy src/documentation over from trunk and then
> >>add a simple to build.xml
>
On Thu, 2002-11-28 at 17:33, Christian Geisert wrote:
> Hi,
>
> for the documentation for the maintenance release I think the
> best thing is to copy src/documentation over from trunk and then
> add a simple to build.xml
> Comments?
>
> The track.png in status.html n
Victor Mote wrote:
Christian Geisert wrote:
for the documentation for the maintenance release I think the
best thing is to copy src/documentation over from trunk and then
add a simple to build.xml
Comments?
I had a thought left over from our discussion of branching a few weeks ago
that
Christian Geisert wrote:
> for the documentation for the maintenance release I think the
> best thing is to copy src/documentation over from trunk and then
> add a simple to build.xml
> Comments?
I had a thought left over from our discussion of branching a few weeks ago
that might
Geisert wrote:
> for the documentation for the maintenance release I think the
> best thing is to copy src/documentation over from trunk and then
> add a simple to build.xml
> Comments?
>
> The track.png in status.html needs a update. How is it done?
Hi,
for the documentation for the maintenance release I think the
best thing is to copy src/documentation over from trunk and then
add a simple to build.xml
Comments?
The track.png in status.html needs a update. How is it done?
Christian
Will do.
On Sun, 10 Nov 2002 22:58:19 +0200 Oleg Tkachenko wrote:
> Jeremias Maerki wrote:
>
> > It works in my environment. I'd be very grateful if I got feedback if it
> > works for others as well because the changes have quite some impact.
> Nice feature, works like a charm for me. I believe i
Jeremias Maerki wrote:
It works in my environment. I'd be very grateful if I got feedback if it
works for others as well because the changes have quite some impact.
Nice feature, works like a charm for me. I believe it should be
documented along with baseDir and also example of defining fontBas
Oleg,
Thanks for that. I have noticed that there are quite a few people who
do respond on dev-user, in addition to yourself and Keiron, which is why
I wondered whether Joerg was making a specific request. I eventually
concluded he was not.
Peter
Oleg Tkachenko wrote:
Peter B. West wrote:
Christian Geisert wrote:
[Thanks for the gratulations and now back to FOP
(with permission from my wife ;-)]
Welcome to the club :)
The CHANGES files needs to be updated. Best thing would
be if everybody documents his own changes, if not I'll try to
do it from the cvs-commit messages
Here are
Peter B. West wrote:
If you haven't already left, which questions did you have in mind? Is
it your practise to monitor dev-user for questions which nobody else
picks up? Is that the role you want someone else to take over?
I believe he had meant exactly that. People on fop-user seem to help
On 08.11.2002 22:34:35 Christian Geisert wrote:
> [Thanks for the gratulations and now back to FOP
> (with permission from my wife ;-)]
We hope this stays that way. :-)
> OK,
> I'm planing to do the following things for the next maintenance release
>
> Fix for bug #75
J.Pietschmann wrote:
I'm on vacancy from tomorrow on for a bit more than three
weeks, so I can't do this myself.
Who will take care of the unanswered questions while I'm
offline? Oleg?
Sure. Have a nice time on the vacation!
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel
Joerg,
If you haven't already left, which questions did you have in mind? Is
it your practise to monitor dev-user for questions which nobody else
picks up? Is that the role you want someone else to take over?
Enjoy the holiday. Very sensible of you to stay off-line.
Peter
J.Pietschmann wro
Rhett Aultman wrote:
... as soon as I'm done taking the GRE tomorrow (wishes of luck appreciated)...
Consider them wished.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---
J.Pietschmann wrote:
Christian Geisert wrote:
Anybody else (Joerg/Rhett?) working on something with should go
into this last maintenance release?
- update ant.jar, with ant-optional.jar (for style task),
or do something else.
Why?
Who will take care of the unanswered questions while I&#
Rhett Aultman wrote:
I still think it's critical that we put some time into working on the infinite looping
Yes.
I have a bug related to infinite looping assigned to me, and as soon as I'm done taking the GRE tomorrow (wishes of luck appreciated), I'll have the time to devote to it.
Viel Glü
Christian Geisert wrote:
Anybody else (Joerg/Rhett?) working on something with should go
into this last maintenance release?
- update ant.jar, with ant-optional.jar (for style task),
or do something else.
- get rid of buildtools.jar Simply move the hyph taskdef
to the target and use the
ert@;isu-gmbh.de]
Sent: Friday, November 08, 2002 4:35 PM
To: [EMAIL PROTECTED]
Subject: plan for 0.20.5 release
[Thanks for the gratulations and now back to FOP
(with permission from my wife ;-)]
OK,
I'm planing to do the following things for the next maintenance release
Fix for bug #7587 (
[Thanks for the gratulations and now back to FOP
(with permission from my wife ;-)]
OK,
I'm planing to do the following things for the next maintenance release
Fix for bug #7587 (color problems with jpeg images and acrobat
reader 5, patch seems to work, just needs a little testing)
Updat
Christian Geisert wrote:
I haven't had much time recently to work on the next (final)
maintenance release and will be on holiday the next two
weeks (honeymoon ;-)
Hearty congratulations!
but then we really should get the release
out and so I propose the end of the first week of novemb
1 - 100 of 218 matches
Mail list logo
