[GUMP@brutus]: xml-fop-maintenance/xml-fop-maintenance success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project xml-fop-maintenance *no longer* has an issue. Project State : 'Success' Full details are available at: http://brutus.apache.org/gump/public/xml-fop-maintenance/xml-fop-maintenance/index.html That said, some snippets follow: The following annotations were provided: -DEBUG- Sole jar [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes] -INFO- Enable verbose output, due to 1 previous error(s). -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.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) State: Success Elapsed: 54 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -verbose -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop-maintenance] CLASSPATH : /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop-maintenance/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/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-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/public/workspace/xml-batik/batik-20040725/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon/framework/target/avalon-framework-20040725.jar:/usr/local/gump/public/workspace/avalon/framework/impl/target/avalon-framework-impl-20040725.jar:/usr/local/gump/public/workspace/avalon/framework/api/target/avalon-framework-api-20040725.jar- [javadoc] This sentence is different from what would be generated using -breakiterator: [javadoc] M?? [javadoc] /usr/local/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/viewer/UserMessage.java:131: warning - The first sentence is interpreted to be: [javadoc] M??glicher R??ckgabewert @see ButtonDialog [javadoc] This sentence is different from what would be generated using -breakiterator: [javadoc] /usr/local/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/viewer/UserMessage.java:136: warning - The first sentence is interpreted to be: [javadoc] M?? [javadoc] Wert f??r Setzten keines Buttons [javadoc] This sentence is different from what would be generated using -breakiterator: [javadoc] /usr/local/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/viewer/UserMessage.java:142: warning - The first sentence is interpreted to be: [javadoc] Wert f?? [javadoc] Wert f??r Setzten von nur Ja-Button. [javadoc] /usr/local/gump/public/workspace/xml-fop-maintenance/build/src/org/apache/fop/viewer/UserMessage.java:148: warning - The first sentence is interpreted to be: [javadoc] This sentence is different from what would be generated using -breakiterator: [javadoc] Wert f?? [javadoc] Wert f??r
[GUMP@brutus]: xml-fop/xml-fop success
To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project xml-fop *no longer* has an issue. Project State : 'Success' Full details are available at: http://brutus.apache.org/gump/public/xml-fop/xml-fop/index.html That said, some snippets follow: The following annotations were provided: -DEBUG- Sole jar [fop.jar] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/xml-fop/build/classes] -INFO- Enable verbose output, due to 1 previous error(s). -INFO- No license on redistributable project with outputs. The following work was performed: http://brutus.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) State: Success Elapsed: 51 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -verbose -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only gump [Working Directory: /usr/local/gump/public/workspace/xml-fop] CLASSPATH : /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/workspace/xml-fop/build/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/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-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/public/workspace/xml-batik/batik-20040725/lib/batik-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-swing.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-css.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-bridge.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-xml.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-svg-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-awt-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-transcoder.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-gui-util.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-dom.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-ext.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-svggen.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-parser.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-extension.jar:/usr/local/gump/public/workspace/xml-batik/batik-20040725/lib/batik-gvt.jar:/usr/local/gump/public/workspace/avalon/framework/target/avalon-framework-20040725.jar:/usr/local/gump/public/workspace/avalon/framework/impl/target/avalon-framework-impl-20040725.jar:/usr/local/gump/public/workspace/avalon/framework/api/target/avalon-framework-api-20040725.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api.jar:/usr/local/gump/public/workspace/jakarta-commons/io/dist/jakarta-commons-io-20040725.jar:/usr/local/gump/public/workspace/jfor/dist/lib/jfor-20040725.jar:/usr/local/gump/public/workspace/jakarta-servletapi/dist/lib/servlet.jar- [javadoc] Generating /usr/local/gump/public/workspace/xml-fop/build/javadocs/org/apache/fop/svg/PDFTranscoder.html... [javadoc] /usr/local/gump/public/workspace/xml-fop/src/java/org/apache/fop/svg/SVGUserAgent.java:55: warning - @param argument log is not a parameter name. [javadoc] Generating /usr/local/gump/public/workspace/xml-fop/build/javadocs/org/apache/fop/svg/SVGUserAgent.html... [javadoc] Generating /usr/local/gump/public/workspace/xml-fop/build/javadocs/org/apache/fop/svg/SVGUtilities.html... [javadoc] /usr/local/gump/public/workspace/xml-fop/src/java/org/apache/fop/tools/TestConverter.java:163: warning - @param argument pdf is not a parameter name. [javadoc] Generating /usr/local/gump/public/workspace/xml-fop/build/javadocs/org/apache/fop/tools/TestConverter.html... [javadoc] Generating /usr/local/gump/public/workspace/xml-fop/build/javadocs/org/apache/fop/tools/anttasks/Compare.html... [javadoc] Generating /usr/local/gump/public/workspace/xml-fop/build/javadocs/org/apache/fop/tools/anttasks/Fop.html
Bug report for Fop [2004/07/25]
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) |
| | +-+
| | | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| | | MIN=Minor NOR=Normal ENH=Enhancement |
| | | +-+
| | | | Date Posted |
| | | | +--+
| | | | | Description |
| | | | | |
| 635|Opn|Nor|2001-02-18|Doesn't support id= attribute in fo:page-sequence |
| 953|Opn|Nor|2001-03-12|Incorrect hyperlinks area rendering in justified t|
| 1063|New|Nor|2001-03-21|fop does not handle large fo files|
| 1180|New|Maj|2001-04-02|Problem with monospaced font |
| 1859|Opn|Min|2001-05-22|org.apache.fop.apps.Driver.reset() doesn't fully r|
| 1998|New|Nor|2001-06-05|linefeed-treatment not understood |
| 2150|Ass|Maj|2001-06-13|New page with a table-header but without any tabl|
| 2475|Ass|Nor|2001-07-06|Borders don't appear to work in fo:table-row|
| 2740|New|Maj|2001-07-23|multi-page tables sometimes render badly |
| 2909|New|Maj|2001-07-30|Gradient render error |
| 2964|Ass|Nor|2001-08-02|problems with height of cells in tables |
| 2988|New|Maj|2001-08-03|0.19: list-item-label does not stick to list-item-|
| 3044|Ass|Maj|2001-08-08|keep-together not functioning |
| 3280|New|Nor|2001-08-27|PCL Renderer doesn't work |
| 3305|Opn|Nor|2001-08-28|list-block overlapping footnote body |
| 3497|New|Maj|2001-09-07|id already exists error when using span=all attr|
| 3824|New|Blk|2001-09-25|MIF option with tables|
| 4030|New|Nor|2001-10-08|IOException creating Postscript with graphics on S|
| 4126|New|Nor|2001-10-12|FontState.width() returns pts instead of millipts |
| 4226|New|Nor|2001-10-17|The orphans property doesn't seem to work |
| 4388|New|Nor|2001-10-24|Nullpointer exception in the construction of new D|
| 4415|New|Nor|2001-10-25|scaling=uniform does not work on images... |
| 4510|New|Nor|2001-10-30|fo:inline common properties ignored? |
| 4535|New|Maj|2001-10-31|PCL renderer 1.13 not rendering SVG |
| 4767|New|Nor|2001-11-09|SVG text is distored in PDF output|
| 5001|New|Nor|2001-11-21|content-width and content-height ignored? |
| 5010|New|Enh|2001-11-21|Better error reporting needed |
| 5047|Ass|Nor|2001-11-23|Dotted border style is not supported |
| 5124|New|Maj|2001-11-27|fo:block-container is not rendered properly using |
| 5335|Opn|Min|2001-12-10|Text with embedded CID fonts not retrievable from |
| 5655|Ass|Nor|2002-01-02|text-decoration cannot take multiple values |
| 6094|Opn|Maj|2002-01-29|0.20.3rc hangs in endless loop|
| 6237|Opn|Nor|2002-02-05|#xFB01 (fi ligature) produces a sharp? |
| 6305|New|Nor|2002-02-07|Using fo:table-and-caption results in empty output|
| 6427|New|Enh|2002-02-13|Adding additional Type 1 fonts problem|
| 6437|New|Maj|2002-02-13|Tables without fo:table-column don't render |
| 6483|New|Nor|2002-02-15|Table, Loop, footer could not fit on page, moving|
| 6844|New|Nor|2002-03-04|No line breaks inserted in list-item-label|
| 6918|New|Enh|2002-03-06|reference-orientation has no effect |
| 6997|New|Nor|2002-03-09|[PATCH] Row-spanned row data breaks over a page wi|
| 7140|New|Enh|2002-03-15|page-position attribute set to last on condition|
| 7241|New|Nor|2002-03-19|keep-with-previous, keep-with-next only working on|
| 7283|New|Nor|2002-03-20|Table border misaligned when using margin-left in |
| 7337|New|Nor|2002-03-21|border around external image leaves empty space |
| 7487|New|Nor|2002-03-26|break-before=page for table inserts empty page |
| 7496|New|Nor|2002-03-26|The table header borders are not adjusted to the b|
| 7525|New|Cri|2002-03-27|table with spans inside a list-block |
| 7919|New|Cri|2002-04-10|problem to use attribute linefeed-treatment and li|
| 8003|Ass|Maj|2002-04-12|FopImageFactory never releases cached images |
| 8050|New|Nor|2002-04-13|Soft hyphen (shy;) is not handled properly |
| 8321|New|Nor|2002-04-19|from-parent('width') returns 0 for nested tables |
|
Re: Withdrawal of PMC nomination
Glen Mazza wrote: --- Peter B. West [EMAIL PROTECTED] wrote: Jeremias' ideas about factoring out useful stand-alone elements from the combination of FOP and Batik are essential to the direction I am taking with layout and rendering, aside from being a Good Thing in their own right. Yes, I've pulled about 8 methods from the Renderer interface so far, giving Renderer implementors a little more freedom in how they choose to implement one. Also, I removed direct FOTreeBuilder.addElementMapping() methods which should HEAD a little bit more FAD-friendly (FAD, of course, doesn't have element mappings). The external user sets them in FOUserAgent instead, and HEAD's FOTreeBuilder reads from the FOUserAgent object to obtain them. The FAD version of an FOTreeBuilder would simply ignore this setting. This doesn't mean I'm trying to move to FAD's pull parsing--I'm not-- Shucks. but if I can increase the number of components you can use, so much the better. (To that end, notice the one-line of code in getDefaultHandler() in Driver that initializes FOTreeBuilder. If FAD's FOTreeBuilder equivalent can work with these arguments--a render type, output stream, FOUserAgent object--great! That would mean fop.apps package can be the same between two systems.) I think there are some possibilities here. A lot of what you are doing seems kindred (in spirit, at least) with Victor's approach. I'll take whatever I can get from FOP for FAD, and the more commonality the better. But there is a fundamental difference in approach to XML events in pull parsing, which liberates application processing to a degree which I don't think is appreciated by habituated SAX users. In FAD the scope of XML parsing is entirely circumscribed by the parser thread, which runs on-demand. All of the requirements for inputs, transformations, etc, are the same, because I am using SAX under the hood. But when a native pull parser comes along, say as a result of Andy Clark's work with NekoPull http://www.apache.org/~andyc/neko/doc/pull/index.html, XmlPull http://www.xmlpull.org/, JSR173 Streaming API for XML http://jcp.org/en/jsr/detail?id=173, or the WebLogic XML Streaming API http://e-docs.bea.com/wls/docs70/xml/xml_stream.html, I will happily ditch SAX. Whether the Streaming API will be JAXP compliant is a moot point. If not, it is another wedge between FOP and FAD. In general, I'm trying to move away from supporting direct manipulation of internal objects from external users: e.g., AreaTree.setWidget(), etc. and instead am placing the customization in FOUserAgent (or the xml configuration file, perhaps) for the internal objects to read. That way if an alternative implementation has nothing to do with widgets, it can simply ignore the setting in FOUserAgent without being forced to implement an architecture-breaking setWidget(). This also gives future implementors ability to completely revamp things internally without worrying about the API. The layout engine that I'm currently working on looks as though it will have three threads - a parser thread (which will disappear in a streaming parser), a layout engine and a renderer. Press button=Repeat The Area tree is built in lockstep with the FO tree. An area may provide the context for the resolution of properties on the descendants of the FO that generated that area. The integration is that tight. Furthermore, page layout begins with the start tag of a page-sequence fo:flow, not the end-tag. It is pull parsing that makes this feasible, and makes possible the solution of FOP's most critical problem - memory. It doesn't matter how long the page sequence is in FAD. /Press An API which is to accommodate both FOP and FAD must be able to span such fundamental differences. Incidentally, IIUC, the above is not to do with eager layout. That was a property of layout strategies, concerning how much *layout* context was examined before a final layout decision was taken. In my understanding, it related to the ability to adjust layout across multiple paragraphs or pages in order to find a better quality solution, as opposed to making those decisions based only on local layout information. The same decisions must be made in FAD. However, the first order of business for FAD is to get basic layout working, then demonstrate multi-columns with footnotes, marker processing with inheritance from static-content, floats, keeps, and last-page processing, in no particular order. Peter -- Peter B. West http://cv.pbw.id.au/
Building site with forrest
I have tried to build the site with forrest, without much success. I
had a few problems:
1. Validation error. I solved this problem by creating an OASIS catalog.
2. Files in build/webapps/content are missing. These problems can be solved
by copying src/documentation/content into webapps, or by replacing
in sitemap-0.5.xmap all source references to content/ with
{project:content}, whatever that may mean.
3. File src/documentation/content/xdocs/site.xml is missing. I did not
solve that problem.
Building the target htmldoc causes even more errors.
Are these two indeed broken, or am I doing something wrong?
Regards, Simon
--
Simon Pepping
home page: http://www.leverkruid.nl
Re: fox validation
Thanks. I did not know about the change. It certainly is a better writing style. I am still finishing the details of my documentation. After that I want to work on the layout. Regards, Simon On Fri, Jul 23, 2004 at 09:20:50PM -0700, Glen Mazza wrote: Yes, the way I see it, one of FOP's successes will be our close adherence to JAXP. Another one will be a very strict and solid FO validation component--a firm handshake that hopefully will paint FOP as a Tomcat-like reference implementation for XSL. BTW, Simon, and everyone else, there's about 30 or so validateChildNodes() left to be written--many of them quite complex. Feel free to help out if you'd like! Glen --- J.Pietschmann [EMAIL PROTECTED] wrote: Simon Pepping wrote: The code in Root shows that fox:bookmarks is the only allowed fox child of fo:root. It is not clear that that is true. The web page extensions.html does not even mention fox:bookmarks. The example file examples/fo/basic/pdfoutline.fo clearly embeds fox:outline elements in fox:bookmarks. The docbook stylesheets authors place fox:outline elements directly in fo:root. FOP-0.20.5 has no problem with this arrangement. Even if it is true, it creates compatibility problems. This was changed in the redesign, outlines for bookmarks must now be put into a fox:bookmark. Yes, this is incompatible but cleans up pathological cases like fo:root fox:outline.../fox:outline fo:layout-master-set ... / fox:outline.../fox:outline fo:page-sequence /fo:page-sequence fox:outline.../fox:outline fo:page-sequence /fo:page-sequence /fo:root Some bookmarks in the above case wont be rendered, and it's quite difficult to reliably check for this condition. If there can only be a single fox:bookmark, error checking is much easier. Some would also claim it enforces better writing style. J.Pietschmann -- Simon Pepping home page: http://www.leverkruid.nl
Committing documentation
I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Committing documentation
On Jul 25, 2004, at 11:43 AM, Simon Pepping wrote: I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon I've been thinking about that, and I think FOP needs to add a new 'Documentation' tab, like the structure for the Forrest[1] documentation[2]. I would probably move much of the content under Using FOP under this other tab (although we could still maintain links from the Home Page if desired, and use a similar navigation structure to what's currently in place). As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab. Web Maestro Clay [1] http://forrest.apache.org/ [2] http://forrest.apache.org/docs/your-project.html
Re: Committing documentation
Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom of any of the FOP site's web pages.) Else, best not to commit it--we can always add a link from the Fop site to the documentation on your home page. If you plan on expanding your writing in the future to other areas of XML document publishing, I would recommend the latter right now, as I wouldn't want you to lose your work. Glen *That Jeremias is most welcome to correct, should I be in error here. --- Simon Pepping [EMAIL PROTECTED] wrote: I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: fox validation
Oh please do... --- Simon Pepping [EMAIL PROTECTED] wrote: After that I want to work on the layout. Regards, Simon
Re: Withdrawal of PMC nomination
Thanks for the elaboration--also the links to the pull parsing sites. Glen --- Peter B. West [EMAIL PROTECTED] wrote: All of the requirements for inputs, transformations, etc, are the same, because I am using SAX under the hood. But when a native pull parser comes along, say as a result of Andy Clark's work with NekoPull http://www.apache.org/~andyc/neko/doc/pull/index.html, XmlPull http://www.xmlpull.org/, JSR173 Streaming API for XML http://jcp.org/en/jsr/detail?id=173, or the WebLogic XML Streaming API http://e-docs.bea.com/wls/docs70/xml/xml_stream.html, I will happily ditch SAX. Whether the Streaming API will be JAXP compliant is a moot point. If not, it is another wedge between FOP and FAD.
Re: Committing documentation
Glen Mazza wrote: Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom No, the contribution is covered by the CLA (which you should have read and signed too ;-) See http://www.apache.org/licenses/#clas, paragraph 2: You hereby grant to the Foundation a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to the Foundation in this paragraph, You reserve all right, title and interest in and to your Contributions. Christian
