blob: 685b7da0e9463253b62cc71a7f04538ab9354673 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
<?xml version="1.0" standalone="no"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
"http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
<document>
<header>
<title>Running FOP</title>
</header>
<body>
<section>
<title>Installation</title>
<section>
<title>Overview</title>
<p>The following software must be installed:</p>
<ul>
<li>Java 1.2.x or later.</li>
<li>FOP. The <jump href="http://xml.apache.org/fop/download.html">FOP distribution</jump> includes all libraries that you will need to run a basic FOP installation. These can be found in the xml-fop/lib directory. These libraries include the following:</li>
<ul>
<li>Apache <jump href="http://xml.apache.org/xerces-j/index.html">Xerces-J</jump> for XML parsing. You can use other XML parsers which support SAX and DOM.</li>
<li>Apache Xalan, an XSLT processor.</li>
<li>Apache <jump href="http://xml.apache.org/batik/">Batik</jump>, an SVG library.</li>
</ul>
<li>Optional Libraries</li>
</ul>
</section>
<section>
<title>Instructions</title>
<p>Basic FOP installation consists of first unzipping the <code>.gz</code> file that is the distribution medium, then unarchiving the resulting <code>.tar</code> file in a directory/folder that is convenient on your system. Please consult your operating system documentation or Zip application software documentation for instructions specific to your site.</p>
</section>
<section>
<title>Problems</title>
<p>Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users have recommended that Mac OSX users use the shell command <code>tar -xzf</code> instead.</p>
</section>
</section>
<section>
<title>Starting FOP as a standalone application</title>
<p>Review the batch file fop.bat or the shell script fop.sh to see how FOP is invoked.</p>
<p>The standard scripts for starting FOP require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is <code>/Library/Java/Home</code>. <strong>Caveat: </strong>We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see <jump href="http://developer.apple.com/java/faq">Java on Mac OSX FAQ</jump> for information as it becomes available.</p>
<p><code>fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-pcl|-ps|-txt|-svg|-at|-print] <outfile></code></p>
<p>[OPTIONS]</p>
<source>
-d debug mode<br/>
-x dump configuration settings<br/>
-q quiet mode<br/>
-c cfg.xml use additional configuration file cfg.xml<br/>
-l lang the language to use for user information<br/></source>
<p>[INPUT]</p>
<source>
infile xsl:fo input file (the same as the next)<br/>
-fo infile xsl:fo input file<br/>
-xml infile xml input file, must be used together with -xsl<br/>
-xsl stylesheet xslt stylesheet<br/></source>
<p>[OUTPUT]</p>
<source>
outfile input will be rendered as pdf file into outfile<br/>
-pdf outfile input will be rendered as pdf file (outfile req'd)<br/>
-awt input will be displayed on screen<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/>
-ps outfile input will be rendered as PostScript 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>[Examples]</p>
<source>
fop foo.fo foo.pdf<br/>
fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)<br/>
fop -xsl foo.xsl -xml foo.xml -pdf foo.pdf<br/>
fop foo.fo -mif foo.mif<br/>
fop foo.fo -print or Fop -print foo.fo<br/>
fop foo.fo -awt<br/></source>
</section>
<section>
<title>Problems</title>
<p>If you have problems running FOP, please have a look at the <jump href="gethelp.html">"How to get Help" page</jump>.</p>
</section>
</body>
</document>
|
