[EMAIL PROTECTED]: Project xml-fop-maintenance (in module xml-fop-maintenance) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop-maintenance has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 8 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop-maintenance : XSL-FO (Formatting Objects) processor (Maintenance branch) Full details are available at: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes] -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/gump_work/build_xml-fop-maintenance_xml-fop-maintenance.html Work Name: build_xml-fop-maintenance_xml-fop-maintenance (Type: Build) Work ended in a state of : Failed Elapsed: 35 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop-maintenance] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-gvt.jar:/usr/local/gump/public/workspace/excalibur/framework/api/target/excalibur-framework-api-29032006.jar:/usr/local/gump/public/workspace/excalibur/framework/impl/target/excalibur-framework-impl-29032006.jar - [style] Warning: the task name style is deprecated. Use xslt instead. [style] Processing /x1/gump/public/workspace/xml-fop-maintenance/build/src/codegen/Times-Bold.xml to /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts/TimesBold.java [style] Loading stylesheet /x1/gump/public/workspace/xml-fop-maintenance/build/src/codegen/font-file.xsl [style] Warning: the task name style is deprecated. Use xslt instead. [style] Processing /x1/gump/public/workspace/xml-fop-maintenance/build/src/codegen/Times-BoldItalic.xml to /x1/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/render/pdf/fonts/TimesBoldItalic.java [style] Loading stylesheet /x1/gump/public/workspace/xml-fop-maintenance/build/src/codegen/font-file.xsl [style] Warning: the task name style is
[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 12 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop : XSL-FO (Formatting Objects) processor Full details are available at: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes] -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/gump_work/build_xml-fop_xml-fop.html Work Name: build_xml-fop_xml-fop (Type: Build) Work ended in a state of : Failed Elapsed: 31 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only package [Working Directory: /usr/local/gump/public/workspace/xml-fop] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-gvt.jar:/usr/local/gump/public/workspace/excalibur/framework/api/target/excalibur-framework-api-29032006.jar:/usr/local/gump/public/workspace/excalibur/framework/impl/target/excalibur-framework-impl-29032006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-29032006.jar:/usr/local/gump/public/workspace/jakarta-commons/io/build/jakarta-commons-io-29032006.jar:/usr/local/gump/public/workspace/jakarta-servletapi/dist/lib/servlet.jar - [javac] location: class org.apache.fop.render.bitmap.PNGRenderer [javac] renderParams = PNGEncodeParam.getDefaultEncodeParam(image); [javac]^ [javac] /x1/gump/public/workspace/xml-fop/src/java/org/apache/fop/render/bitmap/PNGRenderer.java:127: cannot find symbol [javac] symbol : class PNGImageEncoder [javac] location: class org.apache.fop.render.bitmap.PNGRenderer [javac] PNGImageEncoder encoder = new PNGImageEncoder(os, renderParams); [javac] ^ [javac] /x1/gump/public/workspace/xml-fop/src/java/org/apache/fop/render/bitmap/PNGRenderer.java:127: cannot find symbol [javac] symbol : class PNGImageEncoder [javac] location: class
[EMAIL PROTECTED]: Project xml-fop (in module xml-fop) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-fop has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 12 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - xml-fop : XSL-FO (Formatting Objects) processor Full details are available at: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes] -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/xml-fop/xml-fop/gump_work/build_xml-fop_xml-fop.html Work Name: build_xml-fop_xml-fop (Type: Build) Work ended in a state of : Failed Elapsed: 31 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only package [Working Directory: /usr/local/gump/public/workspace/xml-fop] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/junit3.8.1/junit.jar:/usr/local/gump/public/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-script.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-29032006/lib/batik-gvt.jar:/usr/local/gump/public/workspace/excalibur/framework/api/target/excalibur-framework-api-29032006.jar:/usr/local/gump/public/workspace/excalibur/framework/impl/target/excalibur-framework-impl-29032006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-29032006.jar:/usr/local/gump/public/workspace/jakarta-commons/io/build/jakarta-commons-io-29032006.jar:/usr/local/gump/public/workspace/jakarta-servletapi/dist/lib/servlet.jar - [javac] location: class org.apache.fop.render.bitmap.PNGRenderer [javac] renderParams = PNGEncodeParam.getDefaultEncodeParam(image); [javac]^ [javac] /x1/gump/public/workspace/xml-fop/src/java/org/apache/fop/render/bitmap/PNGRenderer.java:127: cannot find symbol [javac] symbol : class PNGImageEncoder [javac] location: class org.apache.fop.render.bitmap.PNGRenderer [javac] PNGImageEncoder encoder = new PNGImageEncoder(os, renderParams); [javac] ^ [javac] /x1/gump/public/workspace/xml-fop/src/java/org/apache/fop/render/bitmap/PNGRenderer.java:127: cannot find symbol [javac] symbol : class PNGImageEncoder [javac] location: class
Help for ressources to generate Rtf with Fop
Title: Message Hello, We are using an Fop 0.20.5. How can we do to generate Rtf instead of Pdf ? If it is possible, where could we find the good "fop.jar" to do that ? Thanks by advance Best regards F. BONNICHON (France)
Re: Help for ressources to generate Rtf with Fop
BONNICHON Franck a écrit : Hello, We are using an Fop 0.20.5. How can we do to generate Rtf instead of Pdf ? If it is possible, where could we find the good fop.jar to do that ? Thanks by advance Best regards F. BONNICHON (France) Bonjour. Je me permet de vous répondre en Français car j'ai vu que vous êtes de France :-). Je suis analyste programmeur en Java JSP pour une petite SSII à Dole (en France, à côté de Dijon). Nous éditons un progiciel de gestion intégré qui permet la gestion complète de l'activité d'une société de service (enregistrement, consultation et modification des clients, achats, stocks, commandes fournisseurs, affaires, exécution chantier, fournisseur, gestion des collaborateurs...). Dans le cadre de l'utilisation de nôtre logiciel, il a été nécessaire de créer des fonctions d'édition de devis, factures, commandes, fiche d'intervention... C'est dans ce but que j'ai mis en place la possibilité d'éditer ces diffarents documents au format PDF grâce à FOP (actuellement en version 0.20.3, je ne suis pas passé en version 0.20.5 car elle n'apportait rien de significatif par rapport à l'ancienne). Bref, tout ça pour vous dire qu'en matière de RTF (car j'ai été confronté comme vous à ce souci, je me suis penché et trouvé la solution sur : http://www.codeconsult.ch/jfor/. Vous utiliser FOP, donc vous savez que pour l'obtenir, il se base sur deux fichiers de type XML et XSL pour en générer un nouveau de type FO. Il récupère ce dernier pour finalement aboutir à du PDF. Et bien JFOR permet d'obtenir du RTF en se basant sur un fichier de type FO (également). Faites un tour sur le site, vous verrez, tout y est expliqué. Bon courage! ;-) -- - Christian MAYEMBA Société SFWan Tél. 03 84 70 95 71 [EMAIL PROTECTED] -
Re: Help for ressources to generate Rtf with Fop
On 29.03.2006 18:43:21 Christian Mayemba wrote: BONNICHON Franck a écrit : Hello, We are using an Fop 0.20.5. How can we do to generate Rtf instead of Pdf ? If it is possible, where could we find the good fop.jar to do that ? Thanks by advance Best regards F. BONNICHON (France) Bonjour. Je me permet de vous répondre en Français car j'ai vu que vous êtes de France :-). Je suis analyste programmeur en Java JSP pour une petite SSII à Dole (en France, à côté de Dijon). Nous éditons un progiciel de gestion intégré qui permet la gestion complète de l'activité d'une société de service (enregistrement, consultation et modification des clients, achats, stocks, commandes fournisseurs, affaires, exécution chantier, fournisseur, gestion des collaborateurs...). Dans le cadre de l'utilisation de nôtre logiciel, il a été nécessaire de créer des fonctions d'édition de devis, factures, commandes, fiche d'intervention... C'est dans ce but que j'ai mis en place la possibilité d'éditer ces diffarents documents au format PDF grâce à FOP (actuellement en version 0.20.3, je ne suis pas passé en version 0.20.5 car elle n'apportait rien de significatif par rapport à l'ancienne). You may want to look into the latest FOP release 0.91beta then. A lot of new functionality. :-) Bref, tout ça pour vous dire qu'en matière de RTF (car j'ai été confronté comme vous à ce souci, je me suis penché et trouvé la solution sur : http://www.codeconsult.ch/jfor/. Vous utiliser FOP, donc vous savez que pour l'obtenir, il se base sur deux fichiers de type XML et XSL pour en générer un nouveau de type FO. Il récupère ce dernier pour finalement aboutir à du PDF. Et bien JFOR permet d'obtenir du RTF en se basant sur un fichier de type FO (également). Faites un tour sur le site, vous verrez, tout y est expliqué. Bon courage! ;-) The alternative is really to upgrade to the latest FOP release (0.91beta) because JFOR has been integrated into Apache FOP. JFOR development has stopped. You can now use FOP to create both PDF and RTF. http://xmlgraphics.apache.org/fop/download.html Jeremias Maerki
Re: svn commit: r389563 - in /xmlgraphics/fop/trunk/src/documentation: content/xdocs/trunk/embedding.xml content/xdocs/trunk/intermediate.xml content/xdocs/trunk/output.xml content/xdocs/trunk/pdfencr
On Tue, Mar 28, 2006 at 08:15:13PM +0200, Jeremias Maerki wrote: I'd be grateful if someone would review my changes here. I'd like to avoid having bugs in our example code again. Thanks! I had a quick look at the embedding page. It looks good and very extensive. I also see a few things that would require correction, e.g. the overview, and in the FOUserAgent example the required output stream is missing. When would you like to have corrections? I have no time right now. Regards, Simon On 28.03.2006 20:10:01 jeremias wrote: Author: jeremias Date: Tue Mar 28 10:10:00 2006 New Revision: 389563 URL: http://svn.apache.org/viewcvs?rev=389563view=rev Log: Adjust documentation to changes in outer API (FopFactory etc.). Jeremias Maerki -- Simon Pepping home page: http://www.leverkruid.nl
Re: svn commit: r389563 - in /xmlgraphics/fop/trunk/src/documentation: content/xdocs/trunk/embedding.xml content/xdocs/trunk/intermediate.xml content/xdocs/trunk/output.xml content/xdocs/trunk/pdfencr
ASAP, of course. :-) I think we need to update the site. I'll look into it again tomorrow morning. Thanks, Simon! On 29.03.2006 21:56:41 Simon Pepping wrote: On Tue, Mar 28, 2006 at 08:15:13PM +0200, Jeremias Maerki wrote: I'd be grateful if someone would review my changes here. I'd like to avoid having bugs in our example code again. Thanks! I had a quick look at the embedding page. It looks good and very extensive. I also see a few things that would require correction, e.g. the overview, and in the FOUserAgent example the required output stream is missing. When would you like to have corrections? I have no time right now. Regards, Simon On 28.03.2006 20:10:01 jeremias wrote: Author: jeremias Date: Tue Mar 28 10:10:00 2006 New Revision: 389563 URL: http://svn.apache.org/viewcvs?rev=389563view=rev Log: Adjust documentation to changes in outer API (FopFactory etc.). Jeremias Maerki -- Simon Pepping home page: http://www.leverkruid.nl Jeremias Maerki
DO NOT REPLY [Bug 39138] - block border-left/right works only if margin-left/right=0 is set
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=39138. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39138 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2006-03-29 21:28 --- I think the borders are only clipped in your case. In an example I've just done, the border displayed nicely and as they should be. What's important to know is that the border to the left and to the right is painted beyond/outside the normal content area of the text. If you set margin-left=0mm you trigger certain rules that make the border appear inside the normal content area. These rules can be found in chapter 5.3.2 in XSL 1.0. If you want me to point out to you exactly why the border isn't shown in your special case, please reopen the issue and attach a full FO file. Your snippet doesn't show the reason why the border isn't painted. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: svn commit: r389563 - in /xmlgraphics/fop/trunk/src/documentation: content/xdocs/trunk/embedding.xml content/xdocs/trunk/intermediate.xml content/xdocs/trunk/output.xml content/xdocs/trunk/pdfencr
What exactly needs correction in the overview? I've reread it and I don't see any problems there. I've republished the site now and I can easily do so again if there's anything else that should be changed. On 29.03.2006 21:56:41 Simon Pepping wrote: On Tue, Mar 28, 2006 at 08:15:13PM +0200, Jeremias Maerki wrote: I'd be grateful if someone would review my changes here. I'd like to avoid having bugs in our example code again. Thanks! I had a quick look at the embedding page. It looks good and very extensive. I also see a few things that would require correction, e.g. the overview, and in the FOUserAgent example the required output stream is missing. When would you like to have corrections? I have no time right now. Regards, Simon On 28.03.2006 20:10:01 jeremias wrote: Author: jeremias Date: Tue Mar 28 10:10:00 2006 New Revision: 389563 URL: http://svn.apache.org/viewcvs?rev=389563view=rev Log: Adjust documentation to changes in outer API (FopFactory etc.). Jeremias Maerki -- Simon Pepping home page: http://www.leverkruid.nl Jeremias Maerki
