<ul>
<li>something that makes decisions where the specifiction indicates
that the user agent should decide</li>
-<li>Fop as the user agent, represented by a class that handles
+<li>FOP as the user agent, represented by a class that handles
various setup and decision values</li>
-<li>an class that handles context for a particular Fop conversion
+<li>an class that handles context for a particular FOP conversion
that can be configured/overridden when embedding</li>
</ul>
</section>
<section>
<title>Setting up Hyphenation</title>
- <p>Fop comes already with some hyphenation patterns. If you
+ <p>FOP comes already with some hyphenation patterns. If you
need a hyphenation pattern which isn't included in the
distribution, do the following:
</p>
</p>
<p>3. If you have build your new hyphenation pattern file
successfully you put the file into the /hyph directoy
- and rebuild Fop. The file will be picked up and added
+ and rebuild FOP. The file will be picked up and added
to the fop.jar.
</p>
</section>
<section>
<title>PDF Bookmarks</title>
<p>
-To use this standard Fop extension, you need to add a namespace entry for
+To use this standard FOP extension, you need to add a namespace entry for
http://xml.apache.org/fop/extensions on the root element. </p>
<p>You can provide outlines inside the root object (but outside
Users can help or get issues resolved by contributing information and examples to the developers.
</p>
<section>
- <title>Get familiar with the Fop related standards</title>
- <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 links at <link href="../resources.html#specs">Specifications</link>.</p>
+ <title>Get familiar with the FOP-related standards</title>
+ <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 links at <link href="../resources.html#specs">Specifications</link>.</p>
</section>
<section>
- <title>Fop's Design</title>
+ <title>FOP's Design</title>
<p>The design for FOP is specified under the <link href="../design/index.html">Design</link> section. This is where the information on how FOP is developed and designed
internally will be kept.
</p>
to <link href="mailto:fop-dev-subscribe@xml.apache.org">fop-dev-subscribe@xml.apache.org</link>
</p>
<p>Sending bug reports and feature requests to the list is a welcome and important contribution to
- developing Fop. </p>
+ developing FOP. </p>
<p>Read also the <link href="http://marc.theaimsgroup.com/?l=fop-dev&r=1&w=2">archive</link>
of the discussion list fop-dev to get an idea of the issues being discussed. </p>
</section>
<title>Look at the developer's code using cvs</title>
<p>Between releases the newest code can be accessed via cvs. To do this you need to install a cvs
client on your computer, if it is not already there. An explanation how to connect to the
- Fop source repository can be found at <link href="http://xml.apache.org/cvs.html">http://xml.apache.org/cvs.html</link>.
+ FOP source repository can be found at <link href="http://xml.apache.org/cvs.html">http://xml.apache.org/cvs.html</link>.
An introduction into cvs and the cvs manual can be found in the
<link href="http://xml.apache.org/library.html">reference library</link>.</p>
<p>All changes to the code repository are sent to a special mailing list. After a cvs commit the diffs are automatically sent to this list. You can subscribe
to fop-cvs@xml.apache.org by sending an email to <link href="mailto:fop-cvs-subscribe@xml.apache.org">
- fop-cvs-subscribe@xml.apache.org</link>. If you want to contribute to the development of Fop you should subscribe,
+ fop-cvs-subscribe@xml.apache.org</link>. If you want to contribute to the development of FOP you should subscribe,
because it is important that you follow changes being made. </p>
</section>
<section id="patches">
The following JARs have been updated: Xerces to version
2.0.1, Xalan to version 2.3.1 and Batik to version 1.5beta2.
</li>
- <li>Fop has been compiled with Jimi support</li>
+ <li>FOP has been compiled with Jimi support</li>
<li>
Logging has been changed from LogKit to Avalon's Logger
Interface
<p>Welcome Jeremias Maerki, Joerg Pietschmann and Peter B. West!</p>
</section>
<section>
- <title>11 March 2002 - Fop 0.20.3 released</title>
+ <title>11 March 2002 - FOP 0.20.3 released</title>
<p>This is a maintenance release, the first version which supports the XSL-FO
Recommendation syntax. See the
<link href="http://marc.theaimsgroup.com/?l=xml-apache-announce&m=101588818821794">
<li>The following JARs have been updated:
Xerces to version 2.0.1, Xalan to version 2.3.1 and Batik to version 1.5beta2.
</li>
- <li>Fop has been compiled with Jimi support this time
+ <li>FOP has been compiled with Jimi support this time
but you still have to download
<link href="http://java.sun.com/products/jimi/">Jimi</link>
and copy it to lib/ to get PNG support (no need to build FOP yourself though).
fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)
fop -xsl foo.xsl -xml foo.xml -pdf foo.pdf
fop foo.fo -mif foo.mif
- fop foo.fo -print or Fop -print foo.fo
+ fop foo.fo -print or fop -print foo.fo
fop foo.fo -awt</source>
<p>PDF encryption is only available if FOP was compiled with encryption support <strong>and</strong> if compatible encryption support is availabe at run time. Currently, only the JCE is supported. Check the <link href="pdfencryption.html">Details</link>.</p>
</section>
projects / xmlgraphics-fop.git / commitdiff