Re: [VOTE] Release of FOP 0.93
On Wed, Dec 27, 2006 at 12:04:19PM +0100, Simon Pepping wrote: I have prepared the release files for the FOP 0.93 release. They were ... Herewith I start a vote on this release. The vote will end in 72 hours, that is, on Saturday 30 December 2006 at noon UTC. Various issues with the dist files were reported. This vote has not passed and the release has been rejected. I have deleted the tag fop/tags/fop-0_93. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: New FOP release: FOP 0.93
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: LineBreaking - looking for design idea
Manuel Mall wrote: Probably should do hyphenation at the same time as it iterates over Knuth elements in the LineLM and looks pretty 'ugly' as it modifies the Knuth elements retrospectively. I'm not sure this will pay off. One note in the TeX book about the Knuth paragraph filling algorithm mentions that it called the expensive hyphenation algorithm less often than the naive line filling algorithm (and therefore run faster!). If we do it in the whitesspace loop we would need a means of adding break opportunities to the data structures at this point. One possible solution would be to simply add a ZWSP char at each normal break opportunity I'd go for a Java break mark object, just to avoid any confusion. and a soft hyphen char at every hyphenation point. This sounds *very* expensive, see above. The other idea Andreas suggested, that is to give each Inline LM the last and first character of the their preceeding/following LM when constructing the LM from the FO is also worth a look. Certainly, but it looks somewhat odd to modify semi-high level APIs to cater for a much more low level algorithm. I find access methods more attractive. J.Pietschmann
Re: LineBreaking - looking for design idea
Manuel Mall wrote: However, what about markers. Their content is only known at layout time isn't it? That's an OOPS factor. However, wouldn't this also be a problem for the current whitespace handling? J.Pietschmann
Re: New FOP release: FOP 0.93
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