<p>BTW: The Apache project knows different roles for contributors, namely 'users', 'developers', 'committers' and the 'Project
Management Committee' (An explanation of these roles can be found <jump href="http://xml.apache.org/roles.html">here</jump>).</p>
</s2>
+
+ <s2 title="Coding Conventions">
+ <p>As mentioned in <jump href="http://xml.apache.org/source.html">Apache XML Project Guidelines</jump>,
+ <em>all Java Language source code in the repository must be written in conformance to the
+ <jump href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Code Conventions
+ for the Java Programming Language</jump> as published by Sun</em>. Additionally we agreed on 4
+ spaces (no tabs) for indenting.</p>
+ <p>If you don't like those conventions, just use your own standards while developing and reformat the source before
+ committing with a tool like <jump href="http://astyle.sourceforge.net/">astyle</jump> (Artistic Style).
+ </p>
+ </s2>
+
<s2 title="Get familiar with the Fop related standards">
<p>At the moment Fop is mainly a tool to render XSL:FO files to pdf. Therefore if you want to contribute to Fop you should become
familiar with these standards. You can find their internet addresses on our <jump href="specs.html">website</jump>.</p>
<p>
<figure width="480" height="260" src="document.jpg" alt="Render Diagram" />
</p>
- <p>The latest version of Fop is 0.20.2 and it supports the xsl:fo candidate release.
+ <p>The latest version of Fop is 0.20.2 and it supports the xsl:fo
+ <jump href="http://www.w3.org/TR/2001/REC-xsl-20011015/">XSL-FO Version 1.0
+ W3C Recommendation</jump>.
You can <jump href="download.html">download</jump>
Fop including a precompiled version, the source code and many example files to
get you started. Pointers to introductions into xsl:fo can be found in the
</p>
<p>FOP is part of Apache's XML project. The homepage of FOP is
<jump href="http://xml.apache.org/fop">http://xml.apache.org/fop</jump>.
-Here you can find information about using and developing with FOP.
+ Here you can find information about using and developing with FOP.
</p>
</s1>
</s1>
<s1 title="FOP Objectives">
<p>The goals of the Apache XML FOP Project are to deliver an XSL FO->PDF formatter that is compliant to at least the Basic
- conformance level described in the W3C Candidate Recommendation 21 November 2000, and that complies with the 11 March 1999 Portable Document
+ conformance level described in the W3C Recommendation from 15 October 2001, and that complies with the 11 March 1999 Portable Document
Format Specification (Version 1.3) from Adobe Systems.
</p>
<s2 title="Specifications">
<ul>
<li><jump href="http://www.w3.org/TR/2001/REC-xsl-20011015/">XSL-FO Recommendation (15 October 2001)</jump></li>
- <li><jump href="http://www.renderx.com/Tests/validator/fo2000.dtd.html">A dtd for the XSL-FO CR from November provided by N. Grigoriev from RenderX</jump></li>
+ <li><jump href="http://www.renderx.com/Tests/validator/fo.dtd.html">A dtd for the XSL-FO Recommendation provided by N. Grigoriev from RenderX</jump></li>
<li><jump href="http://www.w3.org/TR/SVG/">Supported SVG Recommendation (04 September 2001)</jump></li>
<li><jump href="http://www.w3.org/TR/REC-xml">XML Recommendation</jump></li>
<li><jump href="http://www.w3.org/TR/xslt">XSLT Recommendation</jump></li>
<ul>
<li><jump href="http://xml.apache.org/mail/fop-dev/">Apache archive of fop-dev@apache.org</jump></li>
<li><jump href="http://marc.theaimsgroup.com/">External, but easier to browse archive fop-dev@apache.org</jump></li>
+ <li>The Mailing list ARChives (MARC) at the AIMS group: <jump href="http://marc.theaimsgroup.com/?l=fop-dev&r=1&w=2">fop-dev</jump>,
+ <jump href="http://marc.theaimsgroup.com/?l=fop-user&r=1&w=2">fop-user</jump></li>(searchable)
<li>There is an xsl:fo mailing list: www-xsl-fo@w3.org. Subscription info can be found here: <jump href="http://www.w3.org/Mail/Request">
http://www.w3.org/Mail/Request</jump>. And the archive can be found here:
<jump href="http://lists.w3.org/Archives/Public/www-xsl-fo/">http://lists.w3.org/Archives/Public/www-xsl-fo/</jump></li>
</s2>
<s2 title="Starting FOP as an standalone application">
- <p><code>Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-pcl|-txt|-print] <outfile></code></p>
+ <p><code>Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-pcl|-txt|-svg|-at|-print] <outfile></code></p>
<p>[OPTIONS]<br/>
<source>
-d debug mode<br/>
-mif outfile input will be rendered as mif file (outfile req'd)<br/>
-pcl outfile input will be rendered as pcl file (outfile req'd)<br/>
-txt outfile input will be rendered as text file (outfile req'd)<br/>
+ -svg outfile input will be rendered as an svg slides file (outfile req'd)
+ -at outfile representation of area tree as XML (outfile req'd)
-print input file will be rendered and sent to the printer<br/>
see options with "-print help"<br/></source>
</p>
fonts that you have embedded using FOP. The font sizes will be rounded
to an integer value. In future this will be improved.
</p>
+ <p>
+Currently transparency is not supported in PDF so many svg images that
+contain effects or graphics with transparent areas will not be displayed
+correctly.
+ </p>
</s2>
<s2 title="Classes">
</li>
<li><em>PDFTranscoder</em>
<br/>
-used to transcode an svg document into a standalone pdf, via
+used by Batik to transcode an svg document into a standalone pdf, via
PDFDocumentGraphics2D.
</li>
</ul>
</fo:simple-page-master>
</fo:layout-master-set>
- <fo:page-sequence master-name="simple">
+ <fo:page-sequence master-reference="simple">
<fo:static-content flow-name="xsl-region-before">
<fo:block text-align="end"
font-size="10pt"
</fo:simple-page-master>
</fo:layout-master-set>
- <fo:page-sequence master-name="simple">
+ <fo:page-sequence master-reference="simple">
<fo:static-content flow-name="xsl-region-before">
<fo:block text-align="end"
font-size="10pt"
projects / xmlgraphics-fop.git / commitdiff