Re: [VOTE] Release files for fop 1.0
Simon Pepping wrote: The release files for fop 1.0 are now ready for review and the release vote. Thanks for preparing the release. snip/ Please, review and cast your votes before Thu 15 July 19:00h UTC. +1 from me. I downloaded the binary files and run a sample FO file which generated correctly. I also downloaded the source, did a build and run a sample FO File and all looks ok to me. So +1 from me. Chris
Intermediate Format (IF) with placeholder / marker
Hi there, I would need an XML element from any namespace which I can use in the XSL and is not interpreted by FOP and goes into the Intermediate Format (IF) output as it is. I want to use this element as placeholder in the FOP_IF, and in a second step I can modify the FOP Intermediate File for my needs. Is there an element I could use? If not how can I make a new FOP Extension which does this? Any other suggestion how to do this are very welcome!!! Thanks in advance! Greetings, Adam Using FOP Trunk
Re: Intermediate Format (IF) with placeholder / marker
On 13/07/10 19:01, Adam Kovacs wrote: Hi there, I would need an XML element from any namespace which I can use in the XSL and is not interpreted by FOP and goes into the Intermediate Format (IF) output as it is. I want to use this element as placeholder in the FOP_IF, and in a second step I can modify the FOP Intermediate File for my needs. I've been doing this using the area tree (AT) output format, using named blocks as suggested already. It seems to me like the IF is much less useful for modifying before output, because it doesn't seem to preserve identifiers, and omits quite a bit of information you might want. In my case I found that there was no XML level way to tell what blocks were contained in which columns of a multi-column flow; I'd have to do it with geometry using the IF. In the AT output, it's obvious from the XML nesting - each column is a flow within a span for the page's content. So... consider using the area tree output instead. It might be a better fit for your needs. -- Craig Ringer
Re: [VOTE] Release files for fop 1.0
+1 Looks good to me. I've checked various aspects of the release. Thanks a lot, Simon, for your work on the release!! BTW, I've contacted Sally Khudairi (VP, Marketing and Publicity) to talk about creating a press release that puts the 1.0 release in the right light. It's a critical release press-wise, so I'd like to get this right. Not that some people expect too much. Too bad OpenSSL beat us to the 1.0 release by about 3 months. ;-) On 12.07.2010 22:29:17 Simon Pepping wrote: The release files for fop 1.0 are now ready for review and the release vote. The release files were built from: https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0 (created in revision 963413). The release files are found here: http://people.apache.org/~spepping/fop-1_0: 3186f93a314bdcb710bd7cb02d80404c fop-1.0-bin.tar.gz 262da85d77fbca68556bc74e44ecca27 fop-1.0-bin.zip b47043cea49a9291bc0ed369a4150dd3 fop-1.0-bundle.jar 95dcc4c2dd08b4bc88ce9ce1ee88c439 fop-1.0-src.tar.gz 8693ed0f4586d394e547a23625a64d34 fop-1.0-src.zip As partially mentioned earlier, I used the following workaround: jdk6: ant distclean, docs jdk14 without junit: ant dist (which runs the docs target again), maven-artifacts jdk6: junit This uses the trick that forrest is run each time, but does not clean out its target directory. With jdk14 all junit tests fail. I removed junit from the classpath for jdk14, and ran junit after the build with jdk6. forrest also gives problems with jdk6: 0.95/images/update.jpg: No pipeline matched request: 0.95/images/update.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 0.95/images/fix.jpg: No pipeline matched request: 0.95/images/fix.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 0.95/images/add.jpg: No pipeline matched request: 0.95/images/add.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/update.jpg: No pipeline matched request: 1.0/images/update.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/fix.jpg: No pipeline matched request: 1.0/images/fix.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/add.jpg: No pipeline matched request: 1.0/images/add.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 These images are in /images, and the problem does not seem to matter. compliance.pdf: internal-destination or external-destination must be specified in basic-link. As a consequence no compliance.pdf was built. For your perusal I uploaded the build log: build-2010-07-12T22:19:58+02:00.log. Please, review and cast your votes before Thu 15 July 19:00h UTC. +1 from me. -- Simon Pepping home page: http://www.leverkruid.eu Jeremias Maerki
Re: [VOTE] Release files for fop 1.0
I am more than happy to help in AU with this achievement in any way I can - let me know Thanks Martin --- Martin Edge Intellimail International Pty Ltd --- On 14/07/2010, at 12:04 AM, Jeremias Maerki d...@jeremias-maerki.ch wrote: +1 Looks good to me. I've checked various aspects of the release. Thanks a lot, Simon, for your work on the release!! BTW, I've contacted Sally Khudairi (VP, Marketing and Publicity) to talk about creating a press release that puts the 1.0 release in the right light. It's a critical release press-wise, so I'd like to get this right. Not that some people expect too much. Too bad OpenSSL beat us to the 1.0 release by about 3 months. ;-) On 12.07.2010 22:29:17 Simon Pepping wrote: The release files for fop 1.0 are now ready for review and the release vote. The release files were built from: https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0 (created in revision 963413). The release files are found here: http://people.apache.org/~spepping/fop-1_0: 3186f93a314bdcb710bd7cb02d80404c fop-1.0-bin.tar.gz 262da85d77fbca68556bc74e44ecca27 fop-1.0-bin.zip b47043cea49a9291bc0ed369a4150dd3 fop-1.0-bundle.jar 95dcc4c2dd08b4bc88ce9ce1ee88c439 fop-1.0-src.tar.gz 8693ed0f4586d394e547a23625a64d34 fop-1.0-src.zip As partially mentioned earlier, I used the following workaround: jdk6: ant distclean, docs jdk14 without junit: ant dist (which runs the docs target again), maven-artifacts jdk6: junit This uses the trick that forrest is run each time, but does not clean out its target directory. With jdk14 all junit tests fail. I removed junit from the classpath for jdk14, and ran junit after the build with jdk6. forrest also gives problems with jdk6: 0.95/images/update.jpg: No pipeline matched request: 0.95/images/update.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 0.95/images/fix.jpg: No pipeline matched request: 0.95/images/fix.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 0.95/images/add.jpg: No pipeline matched request: 0.95/images/add.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/update.jpg: No pipeline matched request: 1.0/images/update.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/fix.jpg: No pipeline matched request: 1.0/images/fix.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/add.jpg: No pipeline matched request: 1.0/images/add.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 These images are in /images, and the problem does not seem to matter. compliance.pdf: internal-destination or external-destination must be specified in basic-link. As a consequence no compliance.pdf was built. For your perusal I uploaded the build log: build-2010-07-12T22:19:58+02:00.log. Please, review and cast your votes before Thu 15 July 19:00h UTC. +1 from me. -- Simon Pepping home page: http://www.leverkruid.eu Jeremias Maerki
Re: [VOTE] Release files for fop 1.0
Looks good! +1 from me! Thank you! My religion is simple. My religion is kindness. - His Holiness the Dalai Lama of Tibet On Jul 12, 2010, at 1:29 PM, Simon Pepping spepp...@leverkruid.eu wrote: The release files for fop 1.0 are now ready for review and the release vote. The release files were built from: https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0 (created in revision 963413). The release files are found here: http://people.apache.org/~spepping/fop-1_0: 3186f93a314bdcb710bd7cb02d80404c fop-1.0-bin.tar.gz 262da85d77fbca68556bc74e44ecca27 fop-1.0-bin.zip b47043cea49a9291bc0ed369a4150dd3 fop-1.0-bundle.jar 95dcc4c2dd08b4bc88ce9ce1ee88c439 fop-1.0-src.tar.gz 8693ed0f4586d394e547a23625a64d34 fop-1.0-src.zip As partially mentioned earlier, I used the following workaround: jdk6: ant distclean, docs jdk14 without junit: ant dist (which runs the docs target again), maven-artifacts jdk6: junit This uses the trick that forrest is run each time, but does not clean out its target directory. With jdk14 all junit tests fail. I removed junit from the classpath for jdk14, and ran junit after the build with jdk6. forrest also gives problems with jdk6: 0.95/images/update.jpg: No pipeline matched request: 0.95/images/update.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 0.95/images/fix.jpg: No pipeline matched request: 0.95/images/fix.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 0.95/images/add.jpg: No pipeline matched request: 0.95/images/add.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/update.jpg: No pipeline matched request: 1.0/images/update.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/fix.jpg: No pipeline matched request: 1.0/images/fix.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 1.0/images/add.jpg: No pipeline matched request: 1.0/images/add.jpg at map:mount - file:/fsc/source/apache-forrest-0.8/main/webapp/./sitemap.xmap:600:76 These images are in /images, and the problem does not seem to matter. compliance.pdf: internal-destination or external-destination must be specified in basic-link. As a consequence no compliance.pdf was built. For your perusal I uploaded the build log: build-2010-07-12T22:19:58+02:00.log. Please, review and cast your votes before Thu 15 July 19:00h UTC. +1 from me. -- Simon Pepping home page: http://www.leverkruid.eu
Re: Press Release [was: [VOTE] Release files for fop 1.0]
On Tue, Jul 13, 2010 at 04:04:23PM +0200, Jeremias Maerki wrote: BTW, I've contacted Sally Khudairi (VP, Marketing and Publicity) to talk about creating a press release that puts the 1.0 release in the right light. It's a critical release press-wise, so I'd like to get this right. Not that some people expect too much. Too bad OpenSSL beat us to the 1.0 release by about 3 months. ;-) I propose some modifications of your short description. You wrote: Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL formatting objects (XSL-FO by W3C). It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. Output formats currently supported include PDF, PostScript, PCL, AFP and other formats. So, usually you start with an XML file which you turn into XSL-FO describing a text document by means of XSLT (eXtensible stylesheet language transformations, which is the sister spec to XSL-FO). Apache FOP then takes that XSL-FO, formats the document and produces one of the supported output formats (ex. PDF). It is used to produce invoices, insurance policies, technical documentation etc. etc. Millions of pages are produced every year by a pretty large user community around the world. I would like to stress the position of XSL-FO and FOP in the XML tool chain. I also made some other smaller changes. I propose: Apache FOP (Formatting Objects Processor) fills one slot in the chain of XML tools: XML (e.g. Apache Xerces for parsing), XSLT (e.g. Apache Xalan), XSL-FO (e.g. Apache FOP). XSL-FO provides print formatting of XML files, where the XSL-FO file (the format specification) may be created using an XSLT transformation of the XML file. Apache FOP fulfills its role by being a print formatter driven by XSL formatting objects. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to the specified output. Output formats currently supported include PDF, PostScript, PCL, AFP and other formats. Usually one starts with an XML file which is turned into an XSL-FO description of the desired printed document by means of XSLT (eXtensible stylesheet language transformations, which is the sister spec to XSL-FO). Apache FOP then takes that XSL-FO, formats the specified document and produces it in one of the supported output formats (e.g. PDF). Apache FOP is used at to produce invoices, insurance policies, technical documentation etc., both at enterprise level and at personal level. Millions of pages are produced every year by a large user community around the world. The docbook community is an important part of the user community. Simon -- Simon Pepping home page: http://www.leverkruid.eu
Re: P*r*s* R*l*a*e [was: [VOTE] Release files for fop 1.0]
Simon, thanks for helping out but that's exactly what Sally didn't want: talking about this in the open especially with the press release in the subject. Please keep this on private@ for now. To anyone press-related listening in: this is WORK IN PROGRESS and not ready to be published!!! We'll make a public announcement when the release is ready. On 13.07.2010 19:32:18 Simon Pepping wrote: On Tue, Jul 13, 2010 at 04:04:23PM +0200, Jeremias Maerki wrote: BTW, I've contacted Sally Khudairi (VP, Marketing and Publicity) to talk about creating a press release that puts the 1.0 release in the right light. It's a critical release press-wise, so I'd like to get this right. Not that some people expect too much. Too bad OpenSSL beat us to the 1.0 release by about 3 months. ;-) I propose some modifications of your short description. You wrote: snip/ Jeremias Maerki
