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
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 to retrieve
.
-- 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 to support fo:marker
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
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 exec command=forrest to build.xml
Comments?
The track.png in status.html needs a update
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 exec command=forrest to build.xml
Comments?
I had a thought left over from
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 exec command=forrest to build.xml
Comments?
The track.png in status.html needs a update. How is it done?
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 exec command=forrest to build.xml
Comments?
The track.png in status.html needs a update. How is it done?
Jeremias Maerki
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 exec command=forrest to build.xml
Comments?
I had a thought left over from our discussion of branching a few weeks ago
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 exec command=forrest to build.xml
Comments?
I had a thought left over from our discussion of branching
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 november
Hi,
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 ;-) but then we really should get the release
out and so I propose the end of the first week of november
as target date for the release candidate.
Then maybe
by then. That was my only real goal for
maintenance.
Felicitations on your matrimony, BTW.
-Original Message-
From: Christian Geisert [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 16, 2002 1:24 PM
To: [EMAIL PROTECTED]
Subject: Maintenance release
Hi,
I haven't had much time
Hello,
Will the maintenance release in the first week of November support the
keep-together property ?
Thank You!
Shaifali Prakash
CHT / Media Entertainment
San Francisco
email: [EMAIL PROTECTED
[EMAIL PROTECTED] wrote:
Will the maintenance release in the first week of November support the
keep-together property ?
Yes, in exactly the same way as the current version (table rows only).
J.Pietschmann
-
To unsubscribe
]
cc:
10/16/2002 12:38 PM Subject: Re: Maintenance release
Please
Christian Geisert wrote:
Hi,
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 ;-)
Congratulations. The first FOP wedding!
but then we really should get the release
out and so I propose the end
Hi all,
I haven't seen anything about the next maintenance release for about a
week now, but I noticed that there had been some discussion about
basic-link problems.
In the meantime, I have improved the basic-link positioning and also
made it work for external-graphic and foreign-inline
[EMAIL PROTECTED] wrote:
is there a way to clear the image cache in FOP 0.2.0.2?
I saw some documentation suggesting a new static method on FopImageFactory
org.apache.fop.images.FopImageFactory.clearCache();
has this been implemented in newer versions?
Interesting question... looks like
J.Pietschmann wrote:
Hi committers,
as you probably noticed, i started to rummage around in
Bugzilla, searching for bugs still in existence and learning
more about current and persistent problems.
Great work, I hope I can help a bit soon.
[..]
Questions:
Will there be another maintenance
.
Questions:
Will there be another maintenance release before something comes
out of the redesign?
If so, when? Roadmap?
If so, which should be the problems solved? Pick from above or
add whatever you think should be added.
Further question: Is the duplicate id bug fixed in all its
weekend.
Questions:
Will there be another maintenance release before something comes
out of the redesign?
If so, when? Roadmap?
If so, which should be the problems solved? Pick from above or
add whatever you think should be added.
Further question: Is the duplicate id bug fixed in all its
:
Will there be another maintenance release before something comes
out of the redesign?
If so, when? Roadmap?
If so, which should be the problems solved? Pick from above or
add whatever you think should be added.
Further question: Is the duplicate id bug fixed in all its
incarnations?
Oops: The FAQ goes
the fundamental
problems with the current architecture.
Manuel
-Original Message-
From: J.Pietschmann [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 23 April 2002 6:19
To: fop dev
Subject: Cleaning up bugzilla and next maintenance release
...
Questions:
Will there be another maintenance release before
Ok,
I'm ready for the maintenance release ;-)
The attached patch just updates the version number (and removes the JDK 1.1
stuff)
Here is my plan:
Make another release candidate (don't forget to update docs from cvs HEAD)
Give some days for testing (there seem to be a lot of people interested
:19 17/12/2001 +0100, you wrote:
Hi,
so many things to do, so little time...
As mentioned earlier I would like to do some more things for the maintenance
release but I have almost no spare time this week.
Thus my question is: should we release now (X-Mas release ;-) or wait some
more days
PROTECTED]
Sent: Monday, December 17, 2001 1:19 PM
Subject: Maintenance release
Hi,
so many things to do, so little time...
As mentioned earlier I would like to do some more things for the
maintenance
release but I have almost no spare time this week.
Thus my question is: should we
Hi,
I have committed the patch.
I have only update the cvs HEAD docs, I think it will be easier to handle
if we just stick to one version of the docs. Since there is only one
website.
So when the distribution is made the docs should be updated from the main
trunk.
On the plus side you
Hi,
I've taken a first look at the documentation and updated some links etc.
You need to run makedoc in docs/xml-doc to generate the html documentation.
I had a lot of problems to get makedoc.bat to work and after fixing those I
realised that makedoc.sh had already been fixed.
(Doh, should have
I'm really sorry, forgot again the attachment ;-(
Hi,
I've taken a first look at the documentation and updated some links etc.
You need to run makedoc in docs/xml-doc to generate the html documentation.
I had a lot of problems to get makedoc.bat to work and after fixing those I
realised that
Hi,
Arved already proposed 15 Dec as release date.
I think it would be a good idea to do some testing before the actual release,
so we should do a code freeze some days in advance.
What about Monday the 10th ?
Should we make another release candidate?
Christian
Christian Geisert [EMAIL PROTECTED] wrote:
Arved already proposed 15 Dec as release date.
I think it would be a good idea to do some testing before the actual
release,
so we should do a code freeze some days in advance.
What about Monday the 10th ?
Any hope of including my recently-posted
32 matches
Mail list logo
