You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2012/04/15 07:39:54 UTC
svn commit: r813018 [18/24] - in
/websites/staging/xmlgraphics/trunk/content: ./ fop/ fop/0.95/
fop/0.95/images/ fop/1.0/ fop/1.0/images/ fop/dev/ fop/dev/design/
fop/dev/fo/ fop/dev/svg/ fop/fo/ fop/trunk/ fop/trunk/images/
Added: websites/staging/xmlgraphics/trunk/content/fop/fo.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/fo.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/fo.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,395 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+ <head>
+ <title>Apache⢠FOP: XSL-FO Input</title>
+
+ <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+ <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+ </style>
+
+
+
+
+
+ </head>
+
+ <body>
+ <div id="banner">
+ </div>
+
+ <div id="navigation">
+ <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+ <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+ <input type="text" name="q" id="query" /><br />
+ <input type="submit" id="submit" value="Search" />
+</form>
+ </div>
+
+ <div id="bannertext">
+ <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+ <h1>Apache⢠FOP: XSL-FO Input</h1>
+ </div>
+ <p><a href="/">Home</a> » <a href="/fop/">Fop</a></p>
+ </div>
+ <div id="content" class="grid_16"><div class="section-content"><p><subtitle>Basic Help for Using XML, XSLT, and XSL-FO</subtitle><version>$Revision: 1298724 $</version></p>
+<h1 id="overview">Overview</h1>
+<p>Apache⢠FOP uses XSL-FO as input. It is the responsibility of the user to make sure that the XSL-FO submitted to FOP is correct. The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another good FAQ is<fork href="http://www.dpawson.co.uk/xsl/">Dave Pawson's XSL FAQ</fork>.</p>
+<h1 id="xml">XML Issues</h1>
+<h2 id="xml-special-chars">Special Characters</h2>
+<p>When entering special (non-ASCII) characters in XML, the general rule is to use the applicable Unicode character instead of trying to use a character entity as you would with HTML. Remember that HTML is an SGML document type. SGML has a limited character set, which requires it to use character entities to represent special characters. One of the improvements of XML over SGML (and thus HTML) is native support for Unicode. Basic XML has only a handful of character entities, primarily because it doesn't really need more.</p>
+<p>Entities such as <code>&uuml;</code> (u with an umlaut), which work in HTML, will be flagged as undefined entities unless you define them yourself in your DTD. Use the corresponding Unicode character instead. A list of predefined HTML entities and their Unicode codepoints can be found at <a href="http://www.w3.org/TR/html4/sgml/entities.html">Character entity references in HTML 4</a> .</p>
+<p>One common example is <code>&nbsp;</code> , used to obtain a non-breaking space in HTML. In XML, use   instead.</p>
+<p>For other non-ASCII characters, such as the Euro symbol, checkbox, etc., see the <a href="http://www.unicode.org/charts/charindex.html">Unicode Reference By Name</a> document that is found at the <a href="http://www.unicode.org">Unicode Consortium</a> site.</p>
+<p>After finding the correct Unicode codepoint to represent the character, use <a href="http://www.w3.org/TR/2000/REC-xml-20001006#sec-references">XML Character References</a> to put the character into your source XML, XSLT or FO. See the non-breaking-space comments above for an example of the syntax using decimal notation. The following hexadecimal example will result in a Euro sign:
+€
+Getting your XML correctly encoded is only part of the job. If you want the character to display or print correctly (and you probably do), then the selected font must contain the necessary glyph. Because of differences between font encoding methods, and limitations in some font technologies, this can be a troublesome issue, especially for symbol characters. The FOP example file <a href="fo/fonts.fo.pdf">Base-14 Font Character Mapping</a> is a very useful resource in sorting these issues out for the Base-14 fonts. For other fonts, use font editing sofware or operating system utilities (such as the Character Map in most Windows platforms) to determine what characters the font supports.</p>
+<p>An alternative to encoding the character and making it available through a font is to use an embedded graphic to represent the character: GIF, PNG, SVG, etc.</p>
+<h2 id="xml-entity-chars">Entity Characters</h2>
+<p>The handful of basic XML character entities that do exist are the ampersand, apostrophe, less-than, greater-than, and single-quote characters. These are needed to distinguish markup tags from content, and to distinguish character entities from content. To avoid parser complaints about illegal characters and entities in your input, ensure that ampersands in text and attributes are written as &, "<" is written as <, and ">" as >. It is not necessary everywhere, but it is wise to do so anyway, just to be sure.</p>
+<p>Most XML parsers will provide a line number and sometimes a column number for offending characters.</p>
+<p>Review the <a href="http://www.w3.org/XML/">XML Specification</a> or a good tutorial for details of the XML file format.</p>
+<h2 id="xml-encoding">Encoding Issues</h2>
+<p>If the parser complains about illegal bytes or characters in the input, or there are unexpected characters in the output, this is usually the result of a character encoding problem. See the <a href="http://www.dpawson.co.uk/xsl">XSL FAQ</a> for additional information. Many software packages that produce XML, including XSLT processors, use UTF-8 encoding as a default. If you view their output with something not aware of the encoding, like Notepad for Win95/98/ME/NT, funny characters are displayed. A � is a giveaway.</p>
+<h1 id="xslt">XSLT Issues</h1>
+<h2 id="xslt-date">Current Date and Time</h2>
+<p>XSL-FO does not currently have a function for retrieving the current date and time. However, in some cases, XSLT can be used to place the current date and time into the XSL-FO document as it is generated.</p>
+<p>One possibility is to use the<jump href="http://exslt.org/date/index.html">exslt date and time extension</jump>.</p>
+<p>Another possibility is to use java or javascript (or perhaps some other language). Here is an example, using java, that works with Xalan. First, create the appropriate namespace:
+<xsl:stylesheet version="1.0"
+ ...
+ xmlns:java="http://xml.apache.org/xslt/java" exclude-result-prefixes="java"
+ ...
+Next, use the java language to retrieve and format the current date and time. Here is an example template:
+<xsl:template match="TodaysDate">
+ <xsl:value-of select="java:format(java:java.text.SimpleDateFormat.new
+('MMMM d, yyyy, h:mm:ss a (zz)'), java:java.util.Date.new())"/>
+ </xsl:template></p>
+<h1 id="xsl-fo">XSL-FO Issues</h1>
+<h2 id="fo-center-vertical">Vertical Centering</h2>
+<p>To vertically center an image, table, or other item, use display-align="center". See <a href="compliance.html#fo-property-display-align">display-align Compliance</a> for implementation status. Here is a small, self-contained document centering an image on a page:
+<?xml version="1.0"?>
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
+ <fo:layout-master-set>
+ <fo:simple-page-master master-name="content"
+ page-width="210mm" page-height="297mm">
+ <fo:region-body/>
+ </fo:simple-page-master>
+ </fo:layout-master-set>
+ <fo:page-sequence master-reference="content">
+ <fo:flow flow-name="xsl-region-body">
+ <fo:table table-layout="fixed" width="100%">
+ <fo:table-column column-width="proportional-column-width(1)"/>
+ <fo:table-body>
+ <fo:table-row height="297mm">
+ <fo:table-cell display-align="center">
+ <fo:block text-align="center">
+ <fo:external-graphic src="fop.jpg"/>
+ </fo:block>
+ </fo:table-cell>
+ </fo:table-row>
+ </fo:table-body>
+ </fo:table>
+ </fo:flow>
+ </fo:page-sequence>
+</fo:root></p>
+<h2 id="fo-center-table-horizon">Horizontal Centering (Tables)</h2>
+<p>To center a table horizontally, one possibility is to add one column on the left and one on the right which pad the table so that the visible part is centered:
+<?xml version="1.0"?>
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
+ <fo:layout-master-set>
+ <fo:simple-page-master master-name="content"
+ page-width="210mm" page-height="297mm">
+ <fo:region-body/>
+ </fo:simple-page-master>
+ </fo:layout-master-set>
+ <fo:page-sequence master-reference="content">
+ <fo:flow flow-name="xsl-region-body">
+ <fo:table table-layout="fixed" width="100%">
+ <fo:table-column column-width="proportional-column-width(1)"/>
+ <fo:table-column column-width="100mm"/>
+ <fo:table-column column-width="proportional-column-width(1)"/>
+ <fo:table-body>
+ <fo:table-row>
+ <fo:table-cell column-number="2">
+ <fo:block>foo</fo:block>
+ </fo:table-cell>
+ </fo:table-row>
+ </fo:table-body>
+ </fo:table>
+ </fo:flow>
+ </fo:page-sequence>
+</fo:root>
+If your table is more complicated, or if defining borders on individual cells becomes too much work, use the code above and nest your table within the middle cell.</p>
+<h2 id="fo-right-align-table-horizon">Right-Aligning (Tables)</h2>
+<p>To right-align a table, you can use the same approach as above for centering tables. Just remove the last table-column element which causes all the left-over space not used by the columns with a fixed column-width to be assigned to the first column which effectively right-aligns the table.</p>
+<h2 id="fo-oddeven">Recto/Verso Static Content Differences</h2>
+<p>One frequent request is that static content be different between recto pages (right-side or odd-numbered pages typically) and verso pages(left-side or even-numbered pages typically). For example, you may wish to place the page number on the "outer" side of each page. There are examples in the FO distribution and in the <a href="http://www.dpawson.co.uk/xsl/sect3/index.html">XSL FAQ FO section</a> .</p>
+<p>First, define a page master with alternating pages masters for odd and even pages. Then specify appropriate regions in these page masters, giving them different names. Use these names to put different static content in these regions. Here is a self-contained demonstration:
+<?xml version="1.0"?>
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
+ <fo:layout-master-set>
+ <fo:simple-page-master master-name="even"
+ page-height="297mm" page-width="210mm"
+ margin-top="20mm" margin-bottom="20mm"
+ margin-left="25mm" margin-right="25mm">
+ <fo:region-body margin-bottom="20mm"/>
+ <fo:region-after region-name="footer-even" extent="20mm"/>
+ </fo:simple-page-master>
+ <fo:simple-page-master master-name="odd"
+ page-height="297mm" page-width="210mm"
+ margin-top="20mm" margin-bottom="20mm"
+ margin-left="25mm" margin-right="25mm">
+ <fo:region-body margin-bottom="20mm"/>
+ <fo:region-after region-name="footer-odd" extent="20mm"/>
+ </fo:simple-page-master>
+ <fo:page-sequence-master master-name="document">
+ <fo:repeatable-page-master-alternatives>
+ <fo:conditional-page-master-reference odd-or-even="even"
+ master-reference="even"/>
+ <fo:conditional-page-master-reference odd-or-even="odd"
+ master-reference="odd"/>
+ </fo:repeatable-page-master-alternatives>
+ </fo:page-sequence-master>
+ </fo:layout-master-set>
+ <fo:page-sequence master-reference="document">
+ <fo:static-content flow-name="footer-even">
+ <fo:block text-align="start"><fo:page-number/></fo:block>
+ </fo:static-content>
+ <fo:static-content flow-name="footer-odd">
+ <fo:block text-align-last="end"><fo:page-number/></fo:block>
+ </fo:static-content>
+ <fo:flow flow-name="xsl-region-body">
+ <fo:block/>
+ <fo:block break-before="page"/>
+ </fo:flow>
+ </fo:page-sequence>
+</fo:root></p>
+<h2 id="fo-first-page">Making the First Page Special</h2>
+<p>To get a special header on the first page, one possibility is to insert it into the flow instead of the static content. Alternatively, use a page master referring to different page masters for the first page and the rest. Here is a code sample:
+<?xml version="1.0"?>
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
+ <fo:layout-master-set>
+ <fo:simple-page-master master-name="first"
+ page-height="297mm" page-width="210mm"
+ margin-top="20mm" margin-bottom="20mm"
+ margin-left="25mm" margin-right="25mm">
+ <fo:region-body margin-bottom="20mm"/>
+ <fo:region-after region-name="footer-first" extent="20mm"/>
+ </fo:simple-page-master>
+ <fo:simple-page-master master-name="rest"
+ page-height="297mm" page-width="210mm"
+ margin-top="20mm" margin-bottom="20mm"
+ margin-left="25mm" margin-right="25mm">
+ <fo:region-body margin-bottom="20mm"/>
+ <fo:region-after region-name="footer-rest" extent="20mm"/>
+ </fo:simple-page-master>
+ <fo:page-sequence-master master-name="document">
+ <fo:repeatable-page-master-alternatives>
+ <fo:conditional-page-master-reference page-position="first"
+ master-reference="first"/>
+ <fo:conditional-page-master-reference page-position="rest"
+ master-reference="rest"/>
+ </fo:repeatable-page-master-alternatives>
+ </fo:page-sequence-master>
+ </fo:layout-master-set>
+ <fo:page-sequence master-reference="document">
+ <fo:static-content flow-name="footer-first">
+ <fo:block text-align="center">First page.</fo:block>
+ </fo:static-content>
+ <fo:static-content flow-name="footer-rest">
+ <fo:block text-align-last="center">Other page.</fo:block>
+ </fo:static-content>
+ <fo:flow flow-name="xsl-region-body">
+ <fo:block/>
+ <fo:block break-before="page"/>
+ <fo:block break-before="page"/>
+ </fo:flow>
+ </fo:page-sequence>
+</fo:root></p>
+<h2 id="fo-blank-pages">Blank Pages</h2>
+<p>Sometimes it is desirable to insert blank pages within your output, starting, for example, a new chapter on an odd page or an even page. A blank page can be forced by using <code>break-before="page-even"</code> or similar properties, or by a force-page-count="end-on-odd" on a page sequence.</p>
+<p>To write "This page is intentionally left blank" (or something similar) on an intentionally blank page, first define a conditional page master with a page master specific for blank pages. This allows you to specify static content for blank pages (by definition, a page is blank if no content from a flow is rendered on the page). Omit your normal headers and footers, and use (for example) an extended header to print the "..left blank" statement:
+<?xml version="1.0"?>
+<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
+ <fo:layout-master-set>
+ <fo:simple-page-master master-name="normal"
+ page-height="297mm" page-width="210mm"
+ margin-top="20mm" margin-bottom="20mm"
+ margin-left="25mm" margin-right="25mm">
+ <fo:region-body margin-bottom="20mm"/>
+ <fo:region-after region-name="footer-normal" extent="20mm"/>
+ </fo:simple-page-master>
+ <fo:simple-page-master master-name="blank"
+ page-height="297mm" page-width="210mm"
+ margin-top="20mm" margin-bottom="20mm"
+ margin-left="25mm" margin-right="25mm">
+ <fo:region-body/>
+ <fo:region-before region-name="header-blank" extent="297mm"/>
+ </fo:simple-page-master>
+ <fo:page-sequence-master master-name="document">
+ <fo:repeatable-page-master-alternatives>
+ <fo:conditional-page-master-reference blank-or-not-blank="not-blank"
+ master-reference="normal"/>
+ <fo:conditional-page-master-reference blank-or-not-blank="blank"
+ master-reference="blank"/>
+ </fo:repeatable-page-master-alternatives>
+ </fo:page-sequence-master>
+ </fo:layout-master-set>
+ <fo:page-sequence master-reference="document" force-page-count="end-on-even">
+ <fo:static-content flow-name="footer-normal">
+ <fo:block text-align="center">Normal footer</fo:block>
+ </fo:static-content>
+ <fo:static-content flow-name="header-blank">
+ <fo:block space-before="100mm" text-align-last="center">
+ Intentionally left blank.</fo:block>
+ </fo:static-content>
+ <fo:flow flow-name="xsl-region-body">
+ <fo:block/>
+ </fo:flow>
+ </fo:page-sequence>
+</fo:root></p>
+<h2 id="fo-preformat">Preformatting Content</h2>
+<p>Sometimes it is desirable to retain linebreaks and hard spaces, and to get preformatted text to pass through without being changed. The XSL-FO specification provides some properties for this: <a href="http://www.w3.org/TR/xsl11/#white-space-collapse">white-space-collapse</a> and <a href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#white-space-collapse">linefeed-treatment</a> . In FOP, use white-space-collapse="false" on an enclosing block.</p>
+<h2 id="fo-total-pages">Total Document Pages</h2>
+<p>It is frequently desirable to know the total number of pages in a document and to use that number within the document. For example, you might wish to show the page number on the first page as being "page 1 of 12".</p>
+<p>To accomplish this in <strong>XSL 1.0</strong> , place an empty block with an id at the end of the flow:
+<fo:flow ...>
+ ...
+ <fo:block id="last-page"/>
+</fo:flow>
+Get the number of the last page as follows:
+<fo:page-number-citation ref-id="last-page"/>
+This does not work in certain situations: multiple page sequences, an initial page number other than 1, or forcing a certain page count, thereby producing blank pages at the end.</p>
+<p>In <strong>XSL 1.1</strong> , you get another option to do this: make sure an "id" is set on the page-sequence and reference it using fo:page-number-citation-last. First, the page-sequence:
+<fo:page-sequence id="seq1" ...
+After that, reference the last page the page-sequence generates:
+<fo:page-number-citation-last ref-id="seq1"/><warning>There is no reliable way to get the real total page count with FO mechanisms. You can only get <em>page numbers</em> .</warning>
+The FOP library provides a method to get the total page count after an FO document has been rendered. One possibility is to implement your own wrapper to do a dummy rendering, inquire the total page count and then perform the real rendering, passing the total page count to the XSLT processor to splice it into the generated FO. For example:
+import org.apache.fop.apps.<em>;
+import org.xml.sax.</em>;
+import java.io.<em>;
+import javax.xml.transform.</em>;
+import javax.xml.transform.sax.<em>;
+import javax.xml.transform.stream.</em>;</p>
+<p>class rendtest {</p>
+<p>private static FopFactory fopFactory = FopFactory.newInstance();
+ private static TransformerFactory tFactory = TransformerFactory.newInstance();</p>
+<p>public static void main(String args[]) {
+ OutputStream out;
+ try {
+ //Load the stylesheet
+ Templates templates = tFactory.newTemplates(
+ new StreamSource(new File(args[1])));</p>
+<div class="codehilite"><pre> <span class="sr">//</span><span class="n">First</span> <span class="n">run</span> <span class="p">(</span><span class="n">to</span> <span class="sr">/dev/</span><span class="n">null</span><span class="p">)</span>
+ <span class="n">out</span> <span class="o">=</span> <span class="k">new</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">commons</span><span class="o">.</span><span class="n">io</span><span class="o">.</span><span class="n">output</span><span class="o">.</span><span class="n">NullOutputStream</span><span class="p">();</span>
+ <span class="n">FOUserAgent</span> <span class="n">foUserAgent</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFOUserAgent</span><span class="p">();</span>
+ <span class="n">Fop</span> <span class="n">fop</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFop</span><span class="p">(</span><span class="n">MimeConstants</span><span class="o">.</span><span class="n">MIME_PDF</span><span class="p">,</span> <span class="n">foUserAgent</span><span class="p">,</span> <span class="n">out</span><span class="p">);</span>
+ <span class="n">Transformer</span> <span class="n">transformer</span> <span class="o">=</span> <span class="n">templates</span><span class="o">.</span><span class="n">newTransformer</span><span class="p">();</span>
+ <span class="n">transformer</span><span class="o">.</span><span class="n">setParameter</span><span class="p">(</span><span class="s">"page-count"</span><span class="p">,</span> <span class="s">"#"</span><span class="p">);</span>
+ <span class="n">transformer</span><span class="o">.</span><span class="n">transform</span><span class="p">(</span><span class="k">new</span> <span class="n">StreamSource</span><span class="p">(</span><span class="k">new</span> <span class="n">File</span><span class="p">(</span><span class="n">args</span><span class="p">[</span><span class="mi">0</span><span class="p">])),</span>
+ <span class="k">new</span> <span class="n">SAXResult</span><span class="p">(</span><span class="n">fop</span><span class="o">.</span><span class="n">getDefaultHandler</span><span class="p">()));</span>
+
+ <span class="sr">//</span><span class="n">Get</span> <span class="n">total</span> <span class="n">page</span> <span class="n">count</span>
+ <span class="n">String</span> <span class="n">pageCount</span> <span class="o">=</span> <span class="n">Integer</span><span class="o">.</span><span class="n">toString</span><span class="p">(</span><span class="n">driver</span><span class="o">.</span><span class="n">getResults</span><span class="p">()</span><span class="o">.</span><span class="n">getPageCount</span><span class="p">());</span>
+
+ <span class="sr">//</span><span class="n">Second</span> <span class="n">run</span> <span class="p">(</span><span class="n">the</span> <span class="n">real</span> <span class="n">thing</span><span class="p">)</span>
+ <span class="n">out</span> <span class="o">=</span> <span class="k">new</span> <span class="n">java</span><span class="o">.</span><span class="n">io</span><span class="o">.</span><span class="n">FileOutputStream</span><span class="p">(</span><span class="n">args</span><span class="p">[</span><span class="mi">2</span><span class="p">]);</span>
+ <span class="n">out</span> <span class="o">=</span> <span class="k">new</span> <span class="n">java</span><span class="o">.</span><span class="n">io</span><span class="o">.</span><span class="n">BufferedOutputStream</span><span class="p">(</span><span class="n">out</span><span class="p">);</span>
+ <span class="n">try</span> <span class="p">{</span>
+ <span class="n">foUserAgent</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFOUserAgent</span><span class="p">();</span>
+ <span class="n">fop</span> <span class="o">=</span> <span class="n">fopFactory</span><span class="o">.</span><span class="n">newFop</span><span class="p">(</span><span class="n">MimeConstants</span><span class="o">.</span><span class="n">MIME_PDF</span><span class="p">,</span> <span class="n">foUserAgent</span><span class="p">,</span> <span class="n">out</span><span class="p">);</span>
+ <span class="n">transformer</span> <span class="o">=</span> <span class="n">templates</span><span class="o">.</span><span class="n">newTransformer</span><span class="p">();</span>
+ <span class="n">transformer</span><span class="o">.</span><span class="n">setParameter</span><span class="p">(</span><span class="s">"page-count"</span><span class="p">,</span> <span class="n">pageCount</span><span class="p">);</span>
+ <span class="n">transformer</span><span class="o">.</span><span class="n">transform</span><span class="p">(</span><span class="k">new</span> <span class="n">StreamSource</span><span class="p">(</span><span class="k">new</span> <span class="n">File</span><span class="p">(</span><span class="n">args</span><span class="p">[</span><span class="mi">0</span><span class="p">])),</span>
+ <span class="k">new</span> <span class="n">SAXResult</span><span class="p">(</span><span class="n">fop</span><span class="o">.</span><span class="n">getDefaultHandler</span><span class="p">()));</span>
+ <span class="p">}</span> <span class="n">finally</span> <span class="p">{</span>
+ <span class="n">out</span><span class="o">.</span><span class="nb">close</span><span class="p">();</span>
+ <span class="p">}</span>
+<span class="p">}</span> <span class="n">catch</span><span class="p">(</span> <span class="n">Exception</span> <span class="n">e</span><span class="p">)</span> <span class="p">{</span>
+ <span class="n">e</span><span class="o">.</span><span class="n">printStackTrace</span><span class="p">();</span>
+<span class="p">}</span>
+</pre></div>
+
+
+<p>}
+}
+Declare and use the parameter "page-count" in your XSLT.
+<warning>It is possible to run into a convergence problem with this solution. Replacing the "#" placeholder in the first run with the actual page count in the second run, may change the total number of pages in the document.</warning></p>
+<h2 id="fo-region-align">Aligning Regions</h2>
+<p>Although it may seem counterintuitive, the regions on a page may overlap. Defining a certain body region does not automatically constrain other regions. Instead, this has to be done explicitly. Sometimes for creative reasons it may be desirable to have the regions overlap. Otherwise, you will want to set them up so that the header does not overlap body content or the body extend into the footer.</p>
+<p>Assuming you wish to keep the regions separate, if you have a header region with an extent of 20mm, you should define a margin for the body region of at least 20mm too. Otherwise the header content may overwrite some stuff in the body region. This applies similarly to the extent of the after region and the bottom margin of the body region.</p>
+<h2 id="fo-lines">Drawing Lines</h2>
+<p>It is frequently desirable to draw lines in a document, as separators, side bars or folding marks. There are several possibilities:</p>
+<ul>
+<li>
+<p>Horizontal lines can be drawn using <a href="http://www.w3.org/TR/xsl11/#fo_leader">fo:leader</a> .</p>
+</li>
+<li>
+<p>Use a solid border on a suitable fo:block. This will work for horizontal and vertical lines only.</p>
+</li>
+<li>
+<p>Insert a graphic. GIF, PNG SVG, whatever.</p>
+</li>
+</ul>
+<h2 id="fo-validate">Validating XSL-FO</h2>
+<p><a href="http://www.renderx.com">RenderX</a> has provided an <a href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for FO Documents</a> , which may be helpful in validating general FO issues.</p>
+<p>FOP also maintains an <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop.xsd?view=co">Unofficial FOP Schema</a> in the FOP Subversion Repository. This document can be used either to validate against the FO standard, or against the actual FOP implementation. See the notes near the beginning of the document for instructions on how to use it.</p>
+<h2 id="landscape">Producing landscape pages</h2>
+<p>Pages in landscape format can easily be produced by exchanging the page-height and page-width values of a simple-page-master element.
+<fo:layout-master-set>
+ <fo:simple-page-master master-name="A4-portrait" page-height="29.7cm" page-width="21cm" [..]>
+ <fo:region-body/>
+ </fo:simple-page-master>
+ <fo:simple-page-master master-name="A4-landscape" page-height="21cm" page-width="29.7cm" [..]>
+ <fo:region-body/>
+ </fo:simple-page-master>
+</fo:layout-master-set></p>
+<h2 id="external-resources">External Resources</h2>
+<p>Resources needed by an XSL-FO file that are external to it (graphics, for example), are defined in the XSL-FO standard as being of type "uri-specification". This is defined in the standard at<jump href="http://www.w3.org/TR/xsl11/#datatype">Section 5.11 Property Datatypes</jump>, which includes a link to the URI standard itself. Refer to the XSL-FO and URI standards themselves for more detailed instructions.</p>
+<p>URIs may be either absolute or relative to a base URI. (See <a href="1.0/configuration.html">FOP: Configuration</a> for information on setting the base URI for a FOP session). Here is an example referencing an external-graphic that is relative to the base URI:
+<fo:external-graphic src="url('images/logo.jpg')"/>
+Here is an example referencing an external-graphic that is an absolute URI on a local filesystem:
+fo:external-graphic src="url('file:d:///images/logo.jpg')"/></p></div></div>
+ <div class="clear"></div>
+
+ <div id="footer">
+ <a alt="Apache Software Foundation" href="http://www.apache.org">
+ <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+ </a>
+ <div class="copyright">
+ <p>
+ Copyright © 2011 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+ trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+ marks mentioned may be trademarks or registered trademarks of their respective owners.
+ <br />
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/align.fo
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/align.fo
------------------------------------------------------------------------------
svn:mime-type = application/xml
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/align.fo.pdf
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/align.fo.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/align2.fo
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/align2.fo
------------------------------------------------------------------------------
svn:mime-type = application/xml
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/align2.fo.pdf
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/align2.fo.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/embed.fo
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/embed.fo
------------------------------------------------------------------------------
svn:mime-type = application/xml
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/embed.fo.pdf
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/embed.fo.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/fonts.fo
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/fonts.fo
------------------------------------------------------------------------------
svn:mime-type = application/xml
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/fonts.fo.pdf
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/fonts.fo.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/size.fo
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/size.fo
------------------------------------------------------------------------------
svn:mime-type = application/xml
Added: websites/staging/xmlgraphics/trunk/content/fop/fo/size.fo.pdf
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/xmlgraphics/trunk/content/fop/fo/size.fo.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added: websites/staging/xmlgraphics/trunk/content/fop/gethelp.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/gethelp.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/gethelp.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,111 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+ <head>
+ <title>Apache⢠FOP: Getting Help</title>
+
+ <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+ <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+ </style>
+
+
+
+
+
+ </head>
+
+ <body>
+ <div id="banner">
+ </div>
+
+ <div id="navigation">
+ <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+ <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+ <input type="text" name="q" id="query" /><br />
+ <input type="submit" id="submit" value="Search" />
+</form>
+ </div>
+
+ <div id="bannertext">
+ <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+ <h1>Apache⢠FOP: Getting Help</h1>
+ </div>
+ <p><a href="/">Home</a> » <a href="/fop/">Fop</a></p>
+ </div>
+ <div id="content" class="grid_16"><div class="section-content"><p><subtitle>Checklist for Finding Appropriate Resources</subtitle><version>$Revision: 1298724 $</version></p>
+<p>The Apache⢠FOP developer community is eager to help you maximize the usefulness of FOP. However, to make wise use of its limited resources, support must be primarily self-service. Go through the following checklist sequentially to determine what kind of help you need, and where to get it:</p>
+<h1 id="underlying">Understand Underlying Technologies</h1>
+<p>If you have a questions about XML, XSLT, or XSL-FO that are not directly related to FOP, please consult resources that are appropriate for those questions. FOP is an implementation of these technologies, and when you use FOP, there is a presumption that you have a working understanding of them. We have included several useful links on our <a href="resources.html">Resources</a> page that may help you get started.</p>
+<h1 id="limitations">Understand FOP's Limitations</h1>
+<p>FOP is a work in progress, and has some limitations.</p>
+<p>FOP does not yet fully comply with the W3C XSL-FO standard. The developers track which standard requirements have been implemented, and have documented these capabilities on the <a href="compliance.html">Compliance</a> page. FOP has other limitations regarding specific output formats, graphic formats, etc. These limitations are noted in appropriate places in the documentation. If these documents appear to be in error, continue down this checklist so that either the document or the software can be corrected. Otherwise, please do not submit mailing list questions or bug reports regarding features documented in the standard, or documented as limitations in other parts of the documentation.</p>
+<p>Please especially do not submit questions asking when a particular feature will be implemented. There are too many unknowns to make even a reasonable estimate. Every time a developer stops to answer such a question, the answer will inevitably be "I don't know", but the time taken to respond is time spent away from development. The only sure way to get a feature implemented is to <a href="#how-to-help">pitch in and help</a> .</p>
+<h1 id="doc">Read the Documentation</h1>
+<p>Review the documentation pages on this site. There is information about how to run FOP, how to embed it, how to add custom fonts etc.</p>
+<h1 id="faq">Check the FAQs</h1>
+<p>Consult the <a href="faq.html">Frequently Asked Questions (FAQ)</a> to see if your question has already been answered.</p>
+<h1 id="user-archive">Review FOP User Mailing List Archive</h1>
+<p>It is possible that your question has already been answered but has not yet found its way into the FAQ. Links to the FOP User mailing list archives are on the <a href="maillist.html#fop-user">Mailing List</a> page.</p>
+<h1 id="existing-issue">Look for an Existing Issue Report</h1>
+<p>See <a href="bugs.html#issues_existing">Reported Issues</a> for instructions on how to use the list of open issues. Review these open issues to see if any match your concerns. If so, please do not post a mailing list question or report another issue, as these will only slow the development team down.</p>
+<h1 id="user-mailing-list">Submit Question to FOP User Mailing List</h1>
+<p>See <a href="maillist.html#fop-user">FOP User Mailing List</a> for details.
+Please don't write to any developer directly. Only if you submit questions to the <a href="maillist.html#fop-user">FOP User Mailing List</a> will other FOP users be able to profit from answers given to your question. Another point is that a developer may have gone inactive or is on holidays in which case you may not get an answer in time.</p>
+<h1 id="enter-issue">Enter an Issue Report</h1>
+<p>If, and only if, you have followed all of the above steps, and believe that there is a bug or needed feature that you would like to report, please enter an issue in Bugzilla. Never use Bugzilla to post questions, only to enter issues that have already been asked on the user mailing list.</p>
+<p>See <a href="bugs.html#issues_new">Reporting New Issues</a> for detailed instructions on how to enter an issue.</p>
+<h1 id="how-to-help">Find Out How You Can Help</h1>
+<p>As stated above, the FOP development team is a limited resource. Most make their livings doing things other than writing and supporting FOP. Perhaps you need a feature from the XSL-FO standard to be implemented right away, or a bug fixed, or a new output format, or .... If so, there are several ways that you can help:</p>
+<ul>
+<li>
+<p>Become a <a href="dev/index.html">FOP developer</a> .</p>
+</li>
+<li>
+<p>Fund a developer (or part of one). There is usually at least one FOP developer who would be glad to devote more time to FOP development if funding were in place.</p>
+</li>
+<li>
+<p>Help out on the user mailing list. Users giving good answers to other users allows developers to focus more on development and less on support.</p>
+</li>
+</ul></div></div>
+ <div class="clear"></div>
+
+ <div id="footer">
+ <a alt="Apache Software Foundation" href="http://www.apache.org">
+ <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+ </a>
+ <div class="copyright">
+ <p>
+ Copyright © 2011 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+ trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+ marks mentioned may be trademarks or registered trademarks of their respective owners.
+ <br />
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
Added: websites/staging/xmlgraphics/trunk/content/fop/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/index.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/index.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,92 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+ <head>
+ <title>Apache⢠FOP</title>
+
+ <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+ <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+ </style>
+
+
+
+
+
+ </head>
+
+ <body>
+ <div id="banner">
+ </div>
+
+ <div id="navigation">
+ <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+ <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+ <input type="text" name="q" id="query" /><br />
+ <input type="submit" id="submit" value="Search" />
+</form>
+ </div>
+
+ <div id="bannertext">
+ <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+ <h1>Apache⢠FOP</h1>
+ </div>
+ <p><a href="/">Home</a> » <a href="/fop/">Fop</a></p>
+ </div>
+ <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="intro">Introduction</h1>
+<p>Apache⢠FOP (Formatting Objects Processor) is a print formatter driven by XSL formatting objects (XSL-FO) and an output independent formatter. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. <a href="1.0/output.html">Output formats</a> currently supported include PDF, PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a lesser extent, RTF and TXT. The primary output target is PDF.</p>
+<p>The Apache⢠FOP project is part of the <a href="http://www.apache.org">Apacheâ¢</a> Software Foundation, which is a wider community of users and developers of open source projects.
+<figure alt="Render Diagram" height="260" src="images/document.jpg" width="480"></figure>
+A stable release of the latest version of FOP ( <a href="1.0/">1.0</a> ) is available. It's the third stable release after the large redesign effort and implements a large subset of the <a href="http://www.w3.org/TR/xsl11/">XSL-FO Version 1.1 W3C Recommendation</a> .</p>
+<p>Support for each of the standard's objects and properties is detailed in <a href="compliance.html">FOP Compliance</a> . <a href="download.html">Download</a> options include a precompiled version, source code, and many example files to get you started. <a href="resources.html">Resources</a> include links to XSL-FO introductions and many other useful references. A checklist for <a href="gethelp.html">Getting Help</a> will guide you toward maximizing the usefulness of FOP.</p>
+<p>FOP is proud to be part of <a href="http://xmlgraphics.apache.org">Apache's XML Graphics project</a> .</p>
+<h1 id="demo">Demonstration</h1>
+<p><figure alt="Formatting Diagram" height="260" src="images/layout.jpg" width="480"></figure>
+This image is a demonstration of a real two page document. The XML data on the left is formatted into the two pages on the right. The document contains static areas that appear on every page, an external graphic, a footnote on the first page, and a table that goes across both pages.</p>
+<p>FOP uses the standard XSL-FO file format as input, lays the content out into pages, then renders it to the requested output. One great advantage of using XSL-FO as input is that XSL-FO is itself an XML file, which means that it can be conveniently created from a variety of sources. The most common method is to convert semantic XML to XSL-FO, using an XSLT transformation.</p>
+<h1 id="objectives">FOP Objectives</h1>
+<p>The goals of the Apache FOP project are to deliver an XSL-FO to PDF formatter that is compliant to at least the Basic conformance level described in the W3C Recommendation from 05 December 2006, and that complies with the November 2001 Portable Document Format Specification (Version 1.4) from Adobe Systems.</p>
+<p>Conformance to the XML 1.0 and 1.1 Recommendations, XSLT 1.0 and 2.0 Recommendations and the XML Namespaces Recommendation is understood. Other relevant documents, such as the XPath and XLink Working Drafts, are referenced as necessary. The FOP Project will attempt to use the latest version of evolving specifications.
+The PDF files on this site are created using Apache FOP.</p></div></div>
+ <div class="clear"></div>
+
+ <div id="footer">
+ <a alt="Apache Software Foundation" href="http://www.apache.org">
+ <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+ </a>
+ <div class="copyright">
+ <p>
+ Copyright © 2011 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+ trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+ marks mentioned may be trademarks or registered trademarks of their respective owners.
+ <br />
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
Added: websites/staging/xmlgraphics/trunk/content/fop/knownissues.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/knownissues.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/knownissues.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,193 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+ <head>
+ <title>Apache⢠FOP: Known Issues</title>
+
+ <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+ <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+ </style>
+
+
+
+
+
+ </head>
+
+ <body>
+ <div id="banner">
+ </div>
+
+ <div id="navigation">
+ <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+ <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+ <input type="text" name="q" id="query" /><br />
+ <input type="submit" id="submit" value="Search" />
+</form>
+ </div>
+
+ <div id="bannertext">
+ <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+ <h1>Apache⢠FOP: Known Issues</h1>
+ </div>
+ <p><a href="/">Home</a> » <a href="/fop/">Fop</a></p>
+ </div>
+ <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="known-issues-knownissues">Known issues # {#Known+issues}</h1>
+<p>This page lists currently known issues in the Apache⢠FOP codebase. Please note that this list is generated from data in FOP's code repository (Trunk) and may not exactly represent the list of issues in the latest release.</p>
+<p>For additional information on known issues in Apache FOP, please have a look at the following pages, too:</p>
+<ul>
+<li>
+<p><a href="bugs.html">the bug list in Bugzilla</a> </p>
+</li>
+<li>
+<p><a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks">the task list in the Wiki</a> </p>
+</li>
+</ul>
+<p>Apache⢠FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.</p>
+<h2 id="fo-tree-fotree">FO Tree ## {#FO+Tree}</h2>
+<p>This section lists currently disabled test cases in the test suite for the FO tree tests. The data for this section comes from <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/fotree/disabled-testcases.xml">test/fotree/disabled-testcases.xml</a> .</p>
+<p><strong>demo-test-failure.fo</strong> (demo test failure):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </p>
+<p><strong>from-table-column_marker.fo</strong> (Markers and core function evaluation):<br></br>The code currently evaluates this function according to the column in which the marker appears in the source document, rather than the column it is retrieved in.</p>
+<h2 id="layout-engine-layoutengine">Layout Engine ## {#Layout+Engine}</h2>
+<p>This section lists currently disabled test cases in the test suite for the layout engine tests. The data for this section comes from <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/layoutengine/disabled-testcases.xml">test/layoutengine/disabled-testcases.xml</a> .</p>
+<p><strong>block-container_space-before_space-after_3.xml</strong> (Auto-height block-containers produce fences):<br></br>Block-containers with no height currently don't create a fence for spaces as they should (they behave like a normal block).</p>
+<p><strong>block_font-stretch.xml</strong> (font-stretch NYI):<br></br>Font-stretch is not implemented, yet.</p>
+<p><strong>block_linefeed-treatment.xml</strong> (linefeed-treatment):<br></br>Preserved linefeeds in a fo:character are not handled correctly.</p>
+<p><strong>block_white-space-treatment_3.xml</strong> (white-space-treatment):<br></br>White space handling incorrectly stops at fo:inline boundaries when it comes to formatter generated line breaks.</p>
+<p><strong>block_space-before_space-after_8.xml</strong> (Empty blocks produce fences):<br></br>An empty block currently produces a fence for stacking constraints which it shouldn't.</p>
+<p><strong>block_white-space_nbsp_2.xml</strong> (block white-space nbsp 2):<br></br>The nbsp given as an fo:character is not adjustable and therefore the justification does not work in this case.</p>
+<p><strong>block_word-spacing.xml</strong> (block word-spacing):<br></br>Word-spacing may not work as expected.</p>
+<p><strong>block_word-spacing_text-align_justify.xml</strong> (block word-spacing text-align justify):<br></br>Word-spacing may not work as expected.</p>
+<p><strong>external-graphic_oversized.xml</strong> (external-graphic don't shrink):<br></br>Images currently don't shrink so they fit on a page when they are too big and shrinking is allowed to happen (min/opt/max).</p>
+<p><strong>external-graphic_src_uri.xml</strong> (Test case with HTTP URL):<br></br>Doesn't work behind a proxy which requires authorization.</p>
+<p><strong>footnote_space-resolution.xml</strong> (Space Resolution in foot note area):<br></br>Space resolution does not work between footnote regions.</p>
+<p><strong>inline_block_nested_3.xml</strong> (NPE for table inside an inline):<br></br>Placing a table as a child of an fo:inline produces a NullPointerException.</p>
+<p><strong>inline-container_block_nested.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed. The test case contains no checks.</p>
+<p><strong>inline-container_border_padding.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed.</p>
+<p><strong>inline_letter-spacing.xml</strong> (inline letter-spacing):<br></br>Letter-spacing may not work as expected within fo:inline.</p>
+<p><strong>inline_word-spacing.xml</strong> (inline word-spacing):<br></br>Word-spacing may not work as expected within fo:inline.</p>
+<p><strong>inline_word-spacing_text-align_justify.xml</strong> (inline word-spacing text-align justify):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </p>
+<p><strong>leader-alignment.xml</strong> (leader-alignment NYI):<br></br>Leader-alignment is not yet implemented.</p>
+<p><strong>leader_leader-pattern_use-content_bug.xml</strong> (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: <a href="http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html">http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html</a> </p>
+<p><strong>page-breaking_4.xml</strong> (Page breaking doesn't deal with IPD changes):<br></br>Page breaking currently doesn't support changing available IPD between pages of a single page-sequence. Element list generation has to be reset to redetermine line breaks in this case.</p>
+<p><strong>page-breaking_6.xml</strong> (Overflow handing is incomplete):<br></br>Line breaking is not 100% correct when there's too little space. Overflows are not detected and warned.</p>
+<p><strong>page-height_indefinite_simple.xml</strong> (Indefinite page height handling is imcomplete):<br></br>A RuntimeException is thrown for a page of indefinite height. Lots of warnings.</p>
+<p><strong>page-number-citation_background-image.xml</strong> (page-number-citation: Problem with background-image):<br></br>Background-images on page-number-citations are not placed correctly.</p>
+<p><strong>page-number-citation_complex_1.xml</strong> (IDs are not working on all FO elements):<br></br>The "id" attributes are not properly handled for all block-level FO elements.</p>
+<p><strong>page-number-citation_complex_2.xml</strong> (IDs are not working on all FO elements):<br></br>The "id" attributes are not properly handled for all inline-level FO elements.</p>
+<p><strong>region-body_column-count_footnote.xml</strong> (Footnotes in multi-column documents):<br></br>Footnotes may overlap with text of the region-body in multi-column documents.</p>
+<p><strong>region-body_column-count_balance_4col.xml</strong> (Column Balancing problems):<br></br>Situation in a 4-column document where the column balancing doesn't work and even causes some content to disappear.</p>
+<p><strong>region-body_column-count_bug36356.xml</strong> (Column Balancing problems):<br></br>Column balancing doesn't work as expected.</p>
+<p><strong>table-cell_empty_area_with_marker.xml</strong> (table-cell empty area with marker.xml):<br></br>A table-cell producing an empty area does currently not add any markers to a page. See TODO entry in AreaAdditionUtil.</p>
+<p><strong>table_border-width_conditionality.xml</strong> (Border conditionality on table):<br></br>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the indended outcome according to the spec. The test case should be revisited.</p>
+<p><strong>block_shy_linebreaking_hyph.xml</strong> (Soft hyphen with normal hyphenation enabled):<br></br>A soft hyphen should be a preferred as break compared to a normal hyphenation point but is not.</p>
+<p><strong>keep_within-page_multi-column_overflow.xml</strong> (Page-keep not respected in multi-column layout):<br></br>The block should cause overflow in the last column on the page, rather than be broken.</p>
+<p><strong>block-container_reference-orientation_bug36391.xml</strong> (Block Container Reference Orientation Bug):<br></br>An assert is failing</p>
+<p><strong>simple-page-master_writing-mode_rl_region-body_writing-mode-lr.xml</strong> (Writing mode problems):<br></br>Test erroneously depends upon incorrect implementation of writing-mode trait derivation on fo:region-*.</p>
+<h2 id="other-known-issues-otherknownissues">Other known issues ## {#Other+known+issues}</h2>
+<p>This section lists other known issues.</p>
+<ul>
+<li>
+<p>MIF and SVG output support have not been restored, yet.</p>
+</li>
+<li>
+<p>RTF output is inferior to other output formats supported by FOP. For details, please see the "Output Targets" page of the release you're using.</p>
+</li>
+<li>
+<p>Auto table layout is not implemented, yet.</p>
+</li>
+<li>
+<p>Footnotes may overlap with text of the region-body in multi-column documents.</p>
+</li>
+<li>
+<p>Space resolution does not work between footnote regions.</p>
+</li>
+<li>
+<p>There's a problem involving nested block-containers and reference-orientation 180/-180 (Bugzilla #36391)</p>
+</li>
+<li>
+<p>block-containers with no height currently don't create a fence for spaces as they should (they behave like a normal block).</p>
+</li>
+<li>
+<p>Preserved linefeeds in fo:character are not handled correctly.</p>
+</li>
+<li>
+<p>An empty block currently produces a fence for stacking constraints which it shouldn't.</p>
+</li>
+<li>
+<p>There are several small problems around white space handling.</p>
+</li>
+<li>
+<p>Images currently don't shrink so they fit on a page when they are too big and shrinking is allowed to happen.</p>
+</li>
+<li>
+<p>inline-container may not work as expected.</p>
+</li>
+<li>
+<p>letter-spacing and word-spacing properties may not work as expected.</p>
+</li>
+<li>
+<p>leaders with leader-pattern="use-content" may not work as expected.</p>
+</li>
+<li>
+<p>keep-with-previous doesn't work inside tables and lists, yet.</p>
+</li>
+<li>
+<p>If two consecutive pages don't have the same available width, the content currently isn't properly fit into the available space on the new page.</p>
+</li>
+<li>
+<p>background-images on page-number-citations are not placed correctly.</p>
+</li>
+<li>
+<p>Not all FO elements can be referenced by their "id", most notably: table-body, table-header, table-footer and table-row.</p>
+</li>
+<li>
+<p>Border and padding conditionality are not supported on table-cells, yet.</p>
+</li>
+<li>
+<p>Column balancing in multi-column documents may not work as expected (Bugzilla #36356)</p>
+</li>
+</ul></div></div>
+ <div class="clear"></div>
+
+ <div id="footer">
+ <a alt="Apache Software Foundation" href="http://www.apache.org">
+ <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+ </a>
+ <div class="copyright">
+ <p>
+ Copyright © 2011 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+ trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+ marks mentioned may be trademarks or registered trademarks of their respective owners.
+ <br />
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
Added: websites/staging/xmlgraphics/trunk/content/fop/license.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/license.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/license.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,81 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+ <head>
+ <title>Apache⢠FOP License</title>
+
+ <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+ <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+ </style>
+
+
+
+
+
+ </head>
+
+ <body>
+ <div id="banner">
+ </div>
+
+ <div id="navigation">
+ <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+ <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+ <input type="text" name="q" id="query" /><br />
+ <input type="submit" id="submit" value="Search" />
+</form>
+ </div>
+
+ <div id="bannertext">
+ <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+ <h1>Apache⢠FOP License</h1>
+ </div>
+ <p><a href="/">Home</a> » <a href="/fop/">Fop</a></p>
+ </div>
+ <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="License">License</h1>
+<p>All new Apache⢠FOP releases will be licensed under the <strong>Apache⢠License, version 2.0</strong> . Releases until version 0.20.5 are released unter the Apache⢠License, version 1.1.</p>
+<p>To inspect the license terms please consult the LICENSE and NOTICE files in the root directory of the distribution. The full license text can also be accessed via the web from the<jump href="http://www.apache.org/licenses/">Apache Licenses page</jump>.</p>
+<p>Apache FOP comes with a number of libraries all of which are currently coming from within the Apache Software Foundation. These libraries are all licensed under one of the Apache License versions. There is one exception which is "xml-apis.jar" which contains code licensed by the<fork href="http://www.w3.org">W3C</fork>. Please consult the license files included with the libraries in the "lib" directory for details.</p></div></div>
+ <div class="clear"></div>
+
+ <div id="footer">
+ <a alt="Apache Software Foundation" href="http://www.apache.org">
+ <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+ </a>
+ <div class="copyright">
+ <p>
+ Copyright © 2011 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+ trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+ marks mentioned may be trademarks or registered trademarks of their respective owners.
+ <br />
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
Added: websites/staging/xmlgraphics/trunk/content/fop/maillist.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/maillist.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/maillist.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,223 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+ <head>
+ <title>Apache⢠FOP: Mailing List Resources</title>
+
+ <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+ <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+ <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+ </style>
+
+
+
+
+
+ </head>
+
+ <body>
+ <div id="banner">
+ </div>
+
+ <div id="navigation">
+ <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+ <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+ <input type="text" name="q" id="query" /><br />
+ <input type="submit" id="submit" value="Search" />
+</form>
+ </div>
+
+ <div id="bannertext">
+ <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+ <h1>Apache⢠FOP: Mailing List Resources</h1>
+ </div>
+ <p><a href="/">Home</a> » <a href="/fop/">Fop</a></p>
+ </div>
+ <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="general">General Information</h1>
+<p>Before posting questions to any list:</p>
+<ul>
+<li>
+<p>Review the<jump href="http://jakarta.apache.org/site/mail.html">Jakarta Mailing Lists - Guidelines</jump>for general principles about mailing lists.</p>
+</li>
+<li>
+<p>Review "<jump href="http://www.catb.org/~esr/faqs/smart-questions.html">How To Ask Questions The Smart Way</jump>".</p>
+</li>
+<li>
+<p>Send only <em>plain text</em> email messages to any mailing lists. Please do <em>not</em> send html or rtf email, as they do not work well with the archive engines. If you are using Microsoft Outlook, this setting can be found at the "Mail Format" tab of the Tools/Options menu.</p>
+</li>
+<li>
+<p>Use a mail client that respects the <em>References</em> and/or <em>In-Reply-To</em> mail header entries. This is important for mail clients that can display threads as trees. <strong>Compliant mail clients</strong> include Microsoft Outlook, Becky!, KMail, Apple Mail, Ximian Evolution, Mozilla (version 1.2 or greater). Non-compliant mail clients include Microsoft Exchange, Lotus Notes, Internet Mail Service (MUA or MTA), and dtmail.</p>
+</li>
+</ul>
+<p>For help in understanding email acronyms, see the<jump href="http://www.lingo2word.com/lists/acronym_listA.html">Lingo2Word Acronym List</jump>, or the<jump href="http://www.keno.org/web_design/acronyms.htm">Keno Internet Services Internet Glossary</jump>.</p>
+<h1 id="fop-user">Apache⢠FOP Users Mailing List</h1>
+<p>Use this forum to discuss topics of interest to FOP users.</p>
+<h2 id="fop-user-archive">Archives</h2>
+<p>To review the archives, you have several options:</p>
+<ul>
+<li>
+<p>The <a href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/">Apache Mailing List archive</a> (mod_mbox archive, no full-text search, yet).</p>
+</li>
+<li>
+<p>The <a href="http://xmlgraphics.apache.org/mail/fop-users/">Apache Mailing List archive</a> (gzipped mbox files).</p>
+</li>
+<li>
+<p>The<jump href="http://marc.theaimsgroup.com/?l=fop-user&r=1&w=2">Mailing list ARChives</jump>(MARC) at the AIMS group.</p>
+</li>
+<li>
+<p><jump href="http://www.mail-archive.com/fop-users%40xmlgraphics.apache.org/">The Mail Archive</jump>.</p>
+</li>
+<li>
+<p>The<jump href="http://dir.gmane.org/gmane.text.xml.fop.user">GMANE archive</jump>.</p>
+</li>
+<li>
+<p>The<jump href="http://www.nabble.com/FOP---Users-f353.html">Nabble archive</jump>(only posts after May 2005).</p>
+</li>
+<li>
+<p>The<jump href="http://fop-users.markmail.org/">MarkMail archive</jump>.
+If you don't like mailing lists and prefer a forum-like system, have a look at<jump href="http://dir.gmane.org/gmane.text.xml.fop.user">GMANE</jump>or<jump href="http://www.nabble.com/FOP---Users-f353.html">Nabble</jump>. They allow you to post to the mailing list without having to subscribe.</p>
+</li>
+</ul>
+<h2 id="fop-user-subscribe">Subscription Information</h2>
+<ul>
+<li>
+<p>See <a href="http://xmlgraphics.apache.org/mail.html">Apache XML Graphics Mailing Lists</a> for detailed subscription information.</p>
+</li>
+<li>
+<p>To subscribe (digest only): Send email to <a href="mailto:fop-users-digest-subscribe@xmlgraphics.apache.org">fop-users-digest-subscribe@xmlgraphics.apache.org</a> .</p>
+</li>
+<li>
+<p>To <strong>subscribe</strong> fully: Send email to <a href="mailto:fop-users-subscribe@xmlgraphics.apache.org">fop-users-subscribe@xmlgraphics.apache.org</a> .</p>
+</li>
+<li>
+<p>To receive information about the mailing list: Send email to <a href="mailto:fop-users-help@xmlgraphics.apache.org">fop-users-help@xmlgraphics.apache.org</a> .</p>
+</li>
+<li>
+<p>To <strong>unsubscribe</strong> : Send email to <a href="mailto:fop-users-unsubscribe@xmlgraphics.apache.org">fop-users-unsubscribe@xmlgraphics.apache.org</a> .
+You can find the developer mailing list on the <a href="dev/index.html#mail-fop-dev">Development pages</a> .</p>
+</li>
+</ul>
+<h2 id="fop-user-policy">Submitting a Question</h2>
+<p>FOP support is primarily <em>self-service</em> . The FOP User Mailing List serves as a backup to the self-service documentation for cases where either the documentation is deficient or where users have unusual circumstances. FOP developers and users are happy to help answer questions that are <em>appropriate to the forum</em> (i.e. FOP-specific), and that are <em>submitted after appropriate preparation</em> . To ensure that your question is not <strong>abusive</strong> of this policy, please use the following checklist:</p>
+<ul>
+<li>
+<p>Have you followed the <a href="gethelp.html">Getting Help</a> checklist? If not, please do so before submitting your question.</p>
+</li>
+<li>
+<p>Is your question appropriate to the forum? If it is really an XSL-FO question, XSLT question, or PDF question, please see the other resources on this page that are intended to help you get those questions answered.</p>
+</li>
+<li>
+<p>Have you read <a href="#general">Mailing List General Information</a> ? If not please do so before proceeding.</p>
+</li>
+<li>
+<p>Have you stated the version of FOP you are using? Please do so. Usually, it's a good idea to state the JDK/JRE version and the operating system you're using, too.</p>
+</li>
+<li>
+<p>Have you included any detailed error messages? Please do so.</p>
+</li>
+<li>
+<p>Does a proper understanding of your question require inclusion of XSLT code, DocBook source, or other semantic XML? If so, the question is <em>almost certainly not appropriate to this list</em> . In general, the only input documents that are appropriate on this list are XSL-FO snippets. See <a href="1.0/running.html#check-input">Running Xalan</a> for instructions about capturing the XSL-FO document that is actually submitted to FOP. If you haven't examined the XSL-FO document yourself, then you are not yet prepared to formulate a FOP-specific question.</p>
+</li>
+<li>
+<p>If you are providing one or more XSL-FO snippets:</p>
+<ul>
+<li>
+<p>Have you reduced them to the shortest possible complete, <strong>self-contained</strong> document that demonstrates the problem? Please do so.</p>
+</li>
+<li>
+<p>Have you removed images that are not an integral part of the question? Please do so.</p>
+</li>
+<li>
+<p>Have you filtered out confidential material? Please do so.</p>
+</li>
+</ul>
+</li>
+<li>
+<p>If you are including a stack trace:</p>
+<ul>
+<li>
+<p>Is it helpful in finding the problem? If not, please do not submit it.</p>
+</li>
+<li>
+<p>Have you included only those portions that are relevant to the question? If not, please do so.</p>
+</li>
+</ul>
+</li>
+<li>
+<p>Are you attaching large PDF files or screen shots to your message? If so, please consider attaching a minimal, appropriate B&W GIF, JPG or PNG that conveys the necessary information instead. A good alternative is to put the files on a web server.</p>
+</li>
+</ul>
+<h1 id="w3c-xslfo">XSL-FO Mailing List (at W3C)</h1>
+<p>Use this forum to ask general XSL-FO questions.</p>
+<ul>
+<li>
+<p>To review the archive:<jump href="http://lists.w3.org/Archives/Public/www-xsl-fo/">W3C XSL-FO Archives</jump>.</p>
+</li>
+<li>
+<p>Before posting questions to any list, see " <a href="#general">General Information</a> ".</p>
+</li>
+<li>
+<p>Subscription administration information can be found at<jump href="http://www.w3.org/Mail/Request">W3C Mailing List Administrativia</jump>. After reviewing the instructions there, send your subscribe or unsubscribe request to <a href="mailto:www-xsl-fo-request@w3.org">www-xsl-fo-request@w3.org</a> .</p>
+</li>
+</ul>
+<h1 id="yahoogroups-xslfo">XSL-FO Mailing List (at YahooGroups)</h1>
+<p>Use this forum to ask general XSL-FO questions.</p>
+<ul>
+<li>
+<p>Before posting questions to any list, see " <a href="#general">General Information</a> ".</p>
+</li>
+<li>
+<p>The home page for this groups is<jump href="http://groups.yahoo.com/group/XSL-FO">XSL-FO - discussion of XSL Formatting Objects</jump>.</p>
+</li>
+</ul>
+<h1 id="xslt-mulberry">XSLT List (Mulberry Tech)</h1>
+<ul>
+<li>
+<p>Before posting questions to any list, see " <a href="#general">General Information</a> ".</p>
+</li>
+<li>
+<p>Information for using and subscribing can be found at<jump href="http://www.mulberrytech.com/xsl/xsl-list">XSL-List -- Open Forum on XSL</jump>.</p>
+</li>
+</ul></div></div>
+ <div class="clear"></div>
+
+ <div id="footer">
+ <a alt="Apache Software Foundation" href="http://www.apache.org">
+ <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+ </a>
+ <div class="copyright">
+ <p>
+ Copyright © 2011 The Apache Software Foundation, Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+ <br />
+ Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+ trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+ marks mentioned may be trademarks or registered trademarks of their respective owners.
+ <br />
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org