You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Simon Pepping <sp...@leverkruid.eu> on 2006/12/19 21:02:06 UTC
New FOP release: FOP 0.93
As discussed recently, I will prepare a release of FOP, to be named
0.93.
Two issues need to be addressed:
1. I will apply two patches by Richard Wheeldon, to improve memory
usage:
Bug http://issues.apache.org/bugzilla/show_bug.cgi?id=41009, with
patch http://issues.apache.org/bugzilla/attachment.cgi?id=19177
en bug http://issues.apache.org/bugzilla/show_bug.cgi?id=41044, with
patch http://issues.apache.org/bugzilla/attachment.cgi?id=19155.
I will have to study the first patch, as I have not looked at it, and
the bugzilla page contains nobody's comments. I will only apply the
patch if it seems certain that it breaks nothing.
I have studied and commented the second patch, as has Andreas, and I
believe it can be safely applied before the release.
Applying these patches allows us to present a production version whose
memory usage has been trimmed somewhat.
2. With this release it is possible to use the original font metrics,
without generating a special metrics file for FOP.
See
http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200611.mbox/%3c20061113174723.13E4.DEV@jeremias-maerki.ch%3e.
There is no entry for this in the changes file, and there is no
documentation on the website. It is important enough to clarify with
the release. I will try to add some text to the changes file and
perhaps something to the documentation. As I am not familiar with this
material, if someone else can do a better job, please do.
After these changes I will create a branch.
Manuel, can you hold your changes until the branch has been created?
Please, let me know if you have different ideas.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.eu
Re: New FOP release: FOP 0.93
Posted by Simon Pepping <sp...@leverkruid.eu>.
On Sun, Dec 24, 2006 at 10:09:14AM -0600, Jess Holle wrote:
> Is there any sort of time table for a non-alpha/beta 0.9x or 1.0 release?
That is what I am preparing: FOP 0.93 (without beta), to be released
on 2 January 2007.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.eu
Re: New FOP release: FOP 0.93
Posted by Jess Holle <je...@ptc.com>.
Is there any sort of time table for a non-alpha/beta 0.9x or 1.0 release?
--
Jess Holle
Re: New FOP release: FOP 0.93
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
I've just updated my view of the status of the subsystems. Some
additional tweaking might be required.
About the graphic: I might design a new one after a xmas break. If
someone beats me to it, all the better.
On 22.12.2006 20:28:21 Simon Pepping wrote:
> I want to do some rewriting of the file status.html of the web
> site.
>
> Can you give some feedback on the items in the status overview table
> at the bottom?
>
> It would be nice to have a few changes to the image as well: display
> release 0.93 and the future release 1.0 (without DR1). I cannot do
> that.
Jeremias Maerki
Re: New FOP release: FOP 0.93
Posted by Simon Pepping <sp...@leverkruid.eu>.
I want to do some rewriting of the file status.html of the web
site.
Can you give some feedback on the items in the status overview table
at the bottom?
It would be nice to have a few changes to the image as well: display
release 0.93 and the future release 1.0 (without DR1). I cannot do
that.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.eu
Re: New FOP release: FOP 0.93
Posted by Vincent Hennebert <vi...@anyware-tech.com>.
Simon Pepping a écrit :
> On Tue, Dec 19, 2006 at 09:02:06PM +0100, Simon Pepping wrote:
>> As discussed recently, I will prepare a release of FOP, to be named
>> 0.93.
>
> I have committed fixes for the reported issues with the dist files. I
> have also fixed a few other issues I discovered. I have added a few
> important changes to the release note, and I have reset the target
> release date to 9 January 2007.
>
> I have tested the generated source and bin dist files. I could rebuild
> the dist target from the source dist. I have run the junit tests on
> the bin dist, after some fiddling with the targets in the Ant build
> file. I got one failure:
>
> [junit] Testcase: color_1.xml(org.apache.fop.layoutengine.LayoutEngineTestSuite$1): Caused an ERROR
> [junit] Expected XPath expression to evaluate to 'fop-rgb-icc(1.0,0.5,0.0,sRGB,"../../../src/java/org/apache/fop/pdf/sRGB Color Space Profile.icm",1.0,0.5,0.0)', but got '#ff8000' (XPath: //block[4]//text/@color)
>
> which may be due to its dependence on a file in the src directory,
> which is not included in the bin dist.
>
> Please, test the current state of the branch
> xmlgraphics/fop/branches/fop-0_93 as a release candidate. See the
> commit message for the exact changes w.r.t. the rejected release. For
> your convenience I have uploaded one source dist file and one bin dist
> file, see http://people.apache.org/~spepping/.
Hmmm, I was planning to work a bit on Fop during holidays, but obviously
I haven't found the time... I'll get back to work on the release from
next Tuesday on.
Too bad, that fop.bat problem. But well, such problems always appear in
computer science. Thanks for your great work for the release, anyway.
Vincent
Re: New FOP release: FOP 0.93
Posted by Simon Pepping <sp...@leverkruid.eu>.
On Tue, Dec 19, 2006 at 09:02:06PM +0100, Simon Pepping wrote:
> As discussed recently, I will prepare a release of FOP, to be named
> 0.93.
I have committed fixes for the reported issues with the dist files. I
have also fixed a few other issues I discovered. I have added a few
important changes to the release note, and I have reset the target
release date to 9 January 2007.
I have tested the generated source and bin dist files. I could rebuild
the dist target from the source dist. I have run the junit tests on
the bin dist, after some fiddling with the targets in the Ant build
file. I got one failure:
[junit] Testcase: color_1.xml(org.apache.fop.layoutengine.LayoutEngineTestSuite$1): Caused an ERROR
[junit] Expected XPath expression to evaluate to 'fop-rgb-icc(1.0,0.5,0.0,sRGB,"../../../src/java/org/apache/fop/pdf/sRGB Color Space Profile.icm",1.0,0.5,0.0)', but got '#ff8000' (XPath: //block[4]//text/@color)
which may be due to its dependence on a file in the src directory,
which is not included in the bin dist.
Please, test the current state of the branch
xmlgraphics/fop/branches/fop-0_93 as a release candidate. See the
commit message for the exact changes w.r.t. the rejected release. For
your convenience I have uploaded one source dist file and one bin dist
file, see http://people.apache.org/~spepping/.
I intend to generate the dist files and start a vote on the release
somewhere mid next week.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.eu
---------------------------------------------------------------------
Apache XML Graphics Project URL: http://xmlgraphics.apache.org/
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: New FOP release: FOP 0.93
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 22.12.2006 13:29:19 Simon Pepping wrote:
> I edited the release notes, made some changes to the upgrading and
> changes documents.
>
> I position this new release as the stable release. Version 0.20.5 is
> now advertised the previous release. This is apparent in various
> texts, esp. in the release notes and in 0.93/index.html, and in the
> redirects in .htaccess.
>
> Specifically, I made the following changes:
>
> Added to the changes:
> <action context="Code" dev="BD" type="add">
> Added support for the use of Open Type fonts
> </action>
> <action contect="Code" dev="JM" type="update">
> Enabled Copy/Paste from PDF content in Acrobat Reader for text using embedded TrueType fonts.
> </action>
Wasn't me. I've corrected the entry.
> Removed from the known issues in release notes:
> <li>
> Copy/Paste from PDF content in Acrobat Reader is not supported for
> text using embedded TrueType fonts.
> </li>
> <li>
> Block-level content in fo:inlines may produce unwelcome results.
> </li>
> <li>
> White space on direct inline-level children of a marker is not
> handled correctly.
> </li>
> compare with the change entry:
> <action context="Code" dev="AD" type="fix">
> Deferred property resolution for markers until they are actually retrieved,
> which leads to percentages and relative font-sizes now getting the correct
> values. Also deferred white-space-handling for markers.
> </action>
>
> Uncertain status. The linked bug is resolved, but the description does
> not match the description of the bug:
> <li>
> Omitting fo:table-column or having fo:table-column without a column-width
> and attempting to create columns implicitly from the first
> table row is not implemented, yet (<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=35656">Bugzilla #35656</a>).
> </li>
All the combinations here seem to work.
> The possibility to do without font metrics files is only mentioned in
> the changes file.
>
> Please, review.
>
> When I execute Ant's docs target, forrest insists on building a
> linkmap.html file with 0.92 and trunk. I cannot find out where that is
> derived from.
Doesn't happen here. Try a clean build.
> The only thing that remains is copying changes in the 0.93 directory
> of the documentation to the trunk directory. And respond to your
> remarks and edits, of course. Then this branch is ready for tagging
> and release. I target the release to 2 January 2007. That means that
> the vote will take place next week.
Wonderful! Thanks so much.
> Regards, Simon
>
> On Wed, Dec 20, 2006 at 01:13:02PM +0100, Simon Pepping wrote:
> > I created the documentation for version 0.93 (see
> > src/documentation/content/xdocs/0.93) and edited it for the new
> > release version. Please, check it. Especial attention is needed for
> > the new release notes, src/documentation/content/xdocs/relnotes.xml,
> > most of which still have to be written, the FAQ,
> > src/documentation/content/xdocs/faq.xml, the main page of this
> > release, src/documentation/content/xdocs/0.93/index.xml, and the
> > upgrading page, src/documentation/content/xdocs/0.93/upgrading.xml.
>
> --
> Simon Pepping
> home page: http://www.leverkruid.eu
Jeremias Maerki
Re: New FOP release: FOP 0.93
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Dec 22, 2006, at 13:29, Simon Pepping wrote:
Hi Simon,
> <snip />
> Uncertain status. The linked bug is resolved, but the description does
> not match the description of the bug:
> <li>
> Omitting fo:table-column or having fo:table-column without a
> column-width
> and attempting to create columns implicitly from the first
> table row is not implemented, yet (<a href="http://
> issues.apache.org/bugzilla/show_bug.cgi?id=35656">Bugzilla #35656</
> a>).
> </li>
As far as I can see, the testcases that I enabled with the patch
solving the bug indicate that the described issue basically has been
resolved:
table_table-layout_fixed_2.xml shows that FOP correctly handles
columns in case none were specified
table-column_first-row-width does the same for the column-widths
OTOH, these testcases are *very* basic, namely: only test behaviour
in case there is no spanning going on... I'll see if I can add some
checks for creating columns off of cells spanning multiple columns,
although I'm not entirely sure what the behaviour should be:
<fo:table>
<fo:table-body>
<fo:table-cell starts-row="true"
width="20mm" number-columns-spanned="2">
...
Should we create two implicit columns, and distribute the width evenly?
Currently in the code (TableBody.java), two implicit columns are
created, but the cell's width is not yet automatically distributed.
The latter happens only if the cell spans only one column (no
distribution, but simple one-on-one transfer).
Cheers,
Andreas
Re: New FOP release: FOP 0.93
Posted by Simon Pepping <sp...@leverkruid.eu>.
I edited the release notes, made some changes to the upgrading and
changes documents.
I position this new release as the stable release. Version 0.20.5 is
now advertised the previous release. This is apparent in various
texts, esp. in the release notes and in 0.93/index.html, and in the
redirects in .htaccess.
Specifically, I made the following changes:
Added to the changes:
<action context="Code" dev="BD" type="add">
Added support for the use of Open Type fonts
</action>
<action contect="Code" dev="JM" type="update">
Enabled Copy/Paste from PDF content in Acrobat Reader for text using embedded TrueType fonts.
</action>
Removed from the known issues in release notes:
<li>
Copy/Paste from PDF content in Acrobat Reader is not supported for
text using embedded TrueType fonts.
</li>
<li>
Block-level content in fo:inlines may produce unwelcome results.
</li>
<li>
White space on direct inline-level children of a marker is not
handled correctly.
</li>
compare with the change entry:
<action context="Code" dev="AD" type="fix">
Deferred property resolution for markers until they are actually retrieved,
which leads to percentages and relative font-sizes now getting the correct
values. Also deferred white-space-handling for markers.
</action>
Uncertain status. The linked bug is resolved, but the description does
not match the description of the bug:
<li>
Omitting fo:table-column or having fo:table-column without a column-width
and attempting to create columns implicitly from the first
table row is not implemented, yet (<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=35656">Bugzilla #35656</a>).
</li>
The possibility to do without font metrics files is only mentioned in
the changes file.
Please, review.
When I execute Ant's docs target, forrest insists on building a
linkmap.html file with 0.92 and trunk. I cannot find out where that is
derived from.
The only thing that remains is copying changes in the 0.93 directory
of the documentation to the trunk directory. And respond to your
remarks and edits, of course. Then this branch is ready for tagging
and release. I target the release to 2 January 2007. That means that
the vote will take place next week.
Regards, Simon
On Wed, Dec 20, 2006 at 01:13:02PM +0100, Simon Pepping wrote:
> I created the documentation for version 0.93 (see
> src/documentation/content/xdocs/0.93) and edited it for the new
> release version. Please, check it. Especial attention is needed for
> the new release notes, src/documentation/content/xdocs/relnotes.xml,
> most of which still have to be written, the FAQ,
> src/documentation/content/xdocs/faq.xml, the main page of this
> release, src/documentation/content/xdocs/0.93/index.xml, and the
> upgrading page, src/documentation/content/xdocs/0.93/upgrading.xml.
--
Simon Pepping
home page: http://www.leverkruid.eu
Re: New FOP release: FOP 0.93
Posted by Simon Pepping <sp...@leverkruid.eu>.
I created the documentation for version 0.93 (see
src/documentation/content/xdocs/0.93) and edited it for the new
release version. Please, check it. Especial attention is needed for
the new release notes, src/documentation/content/xdocs/relnotes.xml,
most of which still have to be written, the FAQ,
src/documentation/content/xdocs/faq.xml, the main page of this
release, src/documentation/content/xdocs/0.93/index.xml, and the
upgrading page, src/documentation/content/xdocs/0.93/upgrading.xml.
On Wed, Dec 20, 2006 at 10:24:25AM +0100, Simon Pepping wrote:
> Done, and branch xmlgraphics/fop/branches/fop-0_93 created.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.eu
Re: New FOP release: FOP 0.93
Posted by Simon Pepping <sp...@leverkruid.eu>.
Done, and branch xmlgraphics/fop/branches/fop-0_93 created.
On Tue, Dec 19, 2006 at 09:02:06PM +0100, Simon Pepping wrote:
> As discussed recently, I will prepare a release of FOP, to be named
> 0.93.
>
> Two issues need to be addressed:
>
> 1. I will apply two patches by Richard Wheeldon, to improve memory
> usage:
>
> Bug http://issues.apache.org/bugzilla/show_bug.cgi?id=41009, with
> patch http://issues.apache.org/bugzilla/attachment.cgi?id=19177
>
> en bug http://issues.apache.org/bugzilla/show_bug.cgi?id=41044, with
> patch http://issues.apache.org/bugzilla/attachment.cgi?id=19155.
>
> I will have to study the first patch, as I have not looked at it, and
> the bugzilla page contains nobody's comments. I will only apply the
> patch if it seems certain that it breaks nothing.
>
> I have studied and commented the second patch, as has Andreas, and I
> believe it can be safely applied before the release.
>
> Applying these patches allows us to present a production version whose
> memory usage has been trimmed somewhat.
Applied both.
> 2. With this release it is possible to use the original font metrics,
> without generating a special metrics file for FOP.
>
> See
> http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200611.mbox/%3c20061113174723.13E4.DEV@jeremias-maerki.ch%3e.
> There is no entry for this in the changes file, and there is no
> documentation on the website. It is important enough to clarify with
> the release. I will try to add some text to the changes file and
> perhaps something to the documentation. As I am not familiar with this
> material, if someone else can do a better job, please do.
Change was already in the status file (but not on the web site).
Simon
--
Simon Pepping
home page: http://www.leverkruid.eu
Re: New FOP release: FOP 0.93
Posted by Manuel Mall <ma...@apache.org>.
On Wednesday 20 December 2006 05:02, Simon Pepping wrote:
<snip/>
> Manuel, can you hold your changes until the branch has been created?
>
No problems, will wait until the branch is there.
>
> Regards, Simon
Manuel
Re: New FOP release: FOP 0.93
Posted by Simon Pepping <sp...@leverkruid.eu>.
On Tue, Dec 19, 2006 at 09:02:06PM +0100, Simon Pepping wrote:
> As discussed recently, I will prepare a release of FOP, to be named
> 0.93.
I have committed fixes for the reported issues with the dist files. I
have also fixed a few other issues I discovered. I have added a few
important changes to the release note, and I have reset the target
release date to 9 January 2007.
I have tested the generated source and bin dist files. I could rebuild
the dist target from the source dist. I have run the junit tests on
the bin dist, after some fiddling with the targets in the Ant build
file. I got one failure:
[junit] Testcase: color_1.xml(org.apache.fop.layoutengine.LayoutEngineTestSuite$1): Caused an ERROR
[junit] Expected XPath expression to evaluate to 'fop-rgb-icc(1.0,0.5,0.0,sRGB,"../../../src/java/org/apache/fop/pdf/sRGB Color Space Profile.icm",1.0,0.5,0.0)', but got '#ff8000' (XPath: //block[4]//text/@color)
which may be due to its dependence on a file in the src directory,
which is not included in the bin dist.
Please, test the current state of the branch
xmlgraphics/fop/branches/fop-0_93 as a release candidate. See the
commit message for the exact changes w.r.t. the rejected release. For
your convenience I have uploaded one source dist file and one bin dist
file, see http://people.apache.org/~spepping/.
I intend to generate the dist files and start a vote on the release
somewhere mid next week.
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.eu
Re: New FOP release: FOP 0.93
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 19.12.2006 21:02:06 Simon Pepping wrote:
> As discussed recently, I will prepare a release of FOP, to be named
> 0.93.
>
> Two issues need to be addressed:
>
> 1. I will apply two patches by Richard Wheeldon, to improve memory
> usage:
>
> Bug http://issues.apache.org/bugzilla/show_bug.cgi?id=41009, with
> patch http://issues.apache.org/bugzilla/attachment.cgi?id=19177
>
> en bug http://issues.apache.org/bugzilla/show_bug.cgi?id=41044, with
> patch http://issues.apache.org/bugzilla/attachment.cgi?id=19155.
>
> I will have to study the first patch, as I have not looked at it, and
> the bugzilla page contains nobody's comments. I will only apply the
> patch if it seems certain that it breaks nothing.
>
> I have studied and commented the second patch, as has Andreas, and I
> believe it can be safely applied before the release.
>
> Applying these patches allows us to present a production version whose
> memory usage has been trimmed somewhat.
Thanks for taking care of this.
> 2. With this release it is possible to use the original font metrics,
> without generating a special metrics file for FOP.
>
> See
> http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200611.mbox/%3c20061113174723.13E4.DEV@jeremias-maerki.ch%3e.
> There is no entry for this in the changes file, and there is no
> documentation on the website. It is important enough to clarify with
> the release. I will try to add some text to the changes file and
> perhaps something to the documentation. As I am not familiar with this
> material, if someone else can do a better job, please do.
Well, this is still sort of experimental. The old functionality is
unchanged and stable. I'm not so sure about the part without the font
metrics. There wasn't much feedback. If this is to be documented, I'd
prefer if it is marked as experimental.
> After these changes I will create a branch.
>
> Manuel, can you hold your changes until the branch has been created?
>
> Please, let me know if you have different ideas.
>
> Regards, Simon
>
> --
> Simon Pepping
> home page: http://www.leverkruid.eu
Jeremias Maerki