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/12/10 17:00:11 UTC

svn commit: r841434 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/faq.html

Author: buildbot
Date: Mon Dec 10 16:00:10 2012
New Revision: 841434

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/fop/faq.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 10 16:00:10 2012
@@ -1 +1 @@
-1419536
+1419541

Modified: websites/staging/xmlgraphics/trunk/content/fop/faq.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/faq.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/faq.html Mon Dec 10 16:00:10 2012
@@ -444,10 +444,12 @@ then please <a href="bugs.html#issues_ne
 <p>If you used a relative URL, make sure your application has the working directory you expect. Currently FOP does not use the baseDir for resolving relative URLs pointing to font metric files.</p>
 <p>Try also setting the <a href="1.1/configuration.html#general-elements">font-base configuration</a>.</p>
 <h3 id="saxexception-mismatch">2.12. I get a SAXException: Mismatch: page-sequence vs. root (or similar).</h3>
-<p>The full exception usually looks similar to this:
-Mismatch: page-sequence (http://www.w3.org/1999/XSL/Format) vs. root
-        (http://www.w3.org/1999/XSL/Format)
-This exception is usually a follow-up error after another exception. Sometimes the original exception gets swallowed by Xalan's default <code>ErrorListener</code> (should be fixed in the latest Xalan release).</p>
+<p>The full exception usually looks similar to this:</p>
+<div class="codehilite"><pre><span class="err">Mismatch:</span> <span class="err">page-sequence</span> <span class="err">(http:</span><span class="c1">//www.w3.org/1999/XSL/Format) vs. root (http://www.w3.org/1999/XSL/Format)</span>
+</pre></div>
+
+
+<p>This exception is usually a follow-up error after another exception. Sometimes the original exception gets swallowed by Xalan's default <code>ErrorListener</code> (should be fixed in the latest Xalan release).</p>
 <p>The work-around is to set an explicit <code>ErrorListener</code> on the <code>Transformer</code>. The <code>ErrorListener</code> can be as simple as this:</p>
 <div class="codehilite"><pre><span class="kn">import</span> <span class="nn">javax.xml.transform.ErrorListener</span><span class="o">;</span>
 <span class="kn">import</span> <span class="nn">javax.xml.transform.TransformerException</span><span class="o">;</span>
@@ -518,25 +520,28 @@ This exception is usually a follow-up er
 <h3 id="keep-with">3.6. Keep-with-next, keep-with-previous, keep-together don't work.</h3>
 <p>Current FOP releases have extensive support for these properties. The current release, FOP 1.0, still supports the values "always" and "never" only, no numerical values. There may be a few places where keep-* still don't work, this should be very rare.</p>
 <p>The concept is called “blind table”. The table is used for pure layout reasons and is not obvious in the output.</p>
-<p>An example of an image and the image caption to be kept together:
-<fo:table table-layout="fixed" width="100%">
-  <fo:table-column column-width="proportional-column-width(1)"/>
-  <fo:table-body>
-    <fo:table-row keep-with-next="always">
-      <fo:table-cell>
-        <fo:block>
-          <fo:external-graphic src="foo.jpg"/>
-        </fo:block>
-      </fo:table-cell>
-    </fo:table-row>
-    <fo:table-row>
-      <fo:table-cell>
-        <fo:block>Image Caption</fo:block>
-      </fo:table-cell>
-    </fo:table-row>
-  </fo:table-body>
-</fo:table>
-Consider upgrading to the latest version which supports keeps.</p>
+<p>An example of an image and the image caption to be kept together:</p>
+<div class="codehilite"><pre><span class="nt">&lt;fo:table</span> <span class="na">table-layout=</span><span class="s">&quot;fixed&quot;</span> <span class="na">width=</span><span class="s">&quot;100%&quot;</span><span class="nt">&gt;</span>
+  <span class="nt">&lt;fo:table-column</span> <span class="na">column-width=</span><span class="s">&quot;proportional-column-width(1)&quot;</span><span class="nt">/&gt;</span>
+  <span class="nt">&lt;fo:table-body&gt;</span>
+    <span class="nt">&lt;fo:table-row</span> <span class="na">keep-with-next=</span><span class="s">&quot;always&quot;</span><span class="nt">&gt;</span>
+      <span class="nt">&lt;fo:table-cell&gt;</span>
+        <span class="nt">&lt;fo:block&gt;</span>
+          <span class="nt">&lt;fo:external-graphic</span> <span class="na">src=</span><span class="s">&quot;foo.jpg&quot;</span><span class="nt">/&gt;</span>
+        <span class="nt">&lt;/fo:block&gt;</span>
+      <span class="nt">&lt;/fo:table-cell&gt;</span>
+    <span class="nt">&lt;/fo:table-row&gt;</span>
+    <span class="nt">&lt;fo:table-row&gt;</span>
+      <span class="nt">&lt;fo:table-cell&gt;</span>
+        <span class="nt">&lt;fo:block&gt;</span>Image Caption<span class="nt">&lt;/fo:block&gt;</span>
+      <span class="nt">&lt;/fo:table-cell&gt;</span>
+    <span class="nt">&lt;/fo:table-row&gt;</span>
+  <span class="nt">&lt;/fo:table-body&gt;</span>
+<span class="nt">&lt;/fo:table&gt;</span>
+</pre></div>
+
+
+<p>Consider upgrading to the latest version which supports keeps.</p>
 <h3 id="table-missing">3.7. My tables are missing, or missing their content.</h3>
 <p>Check for <code>fo:table-body</code> around the rows. Usually FOP will catch this problem.</p>
 <p>Also, the <code>fo:table-with-caption</code> element is not implemented, tables within such an element are dropped too. FOP generates an error message for this problem. Older DocBook style sheets generate <code>fo:table-with-caption</code> elements, so watch out.</p>
@@ -565,11 +570,17 @@ Consider upgrading to the latest version
 <p>This happens for <code>fo:page-number-citation</code> elements if the citation occurs before FOP formatted the requested page, usually in TOC or index pages. It is caused by the problem that FOP has to guess how much space the yet unknown page number will occupy, and usually the guesses are somewhat off.</p>
 <p>The most recent FOP releases should have this problem fixed. Check whether you can upgrade.</p>
 <h3 id="hyphenation-fails">3.13. Hyphenation does not work.</h3>
-<p>Make sure you have set the language and optionally the country attributes for an appropriate XSL-FO element (fo:page-sequence, fo:block or fo:character):
-<fo:page-sequence language="fi">
-See <a href="1.1/hyphenation.html#support">Hyphenation Support</a> for details and instructions on using hyphenation with FOP.</p>
-<p>Explicitly enable hyphenation for an appropriate XSL-FO element (fo:block, fo:character):
-<fo:block hyphenate="true"></p>
+<p>Make sure you have set the language and optionally the country attributes for an appropriate XSL-FO element (fo:page-sequence, fo:block or fo:character):</p>
+<div class="codehilite"><pre><span class="nt">&lt;fo:page-sequence</span> <span class="na">language=</span><span class="s">&quot;fi&quot;</span><span class="nt">&gt;</span>
+</pre></div>
+
+
+<p>See <a href="1.1/hyphenation.html#support">Hyphenation Support</a> for details and instructions on using hyphenation with FOP.</p>
+<p>Explicitly enable hyphenation for an appropriate XSL-FO element (<code>fo:block</code>, <code>fo:character</code>):</p>
+<div class="codehilite"><pre><span class="nt">&lt;fo:block</span> <span class="na">hyphenate=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>
+</pre></div>
+
+
 <h3 id="indent-inheritance">3.14. When I use margins, my content in a nested table or block-containers gets indented twice. Is this a bug?</h3>
 <p>No, although you might easily think so. The problem has to do with property inheritance of the start-indent and end-indent properties to which the margin properties are mapped. Apache FOP strictly adheres to the XSL-FO specification here which many other commercial FO implementations don't do to better meet end-user expectations. You can make FOP behave like these if you set <code>setBreakIndentInheritanceOnReferenceAreaBoundary(true)</code> on the FOUserAgent. The better way is to reset <code>start-indent</code> and <code>end-indent</code> to "0pt" on table-body or block-container. For further details, please consult the <a href="http://wiki.apache.org/xmlgraphics-fop/IndentInheritance">Wiki page on Indent Inheritance</a>.</p>
 <h3 id="pdf-ps-java2d-differences">3.15. Why is the output of Java2D/AWT-based renderers different than, for example, PDF or PS?</h3>
@@ -630,10 +641,16 @@ See <a href="1.1/hyphenation.html#suppor
 <p>This usually means the selected font doesn't have a glyph for the character.</p>
 <p>The standard text fonts supplied with Acrobat Reader have mostly glyphs for characters from the ISO Latin 1 character set. For a variety of reasons, even those are not completely guaranteed to work, for example you can't use the fi ligature from the standard serif font. Check the <a href="1.1/output.html#pdf-fonts">overview</a> for the default PDF fonts.</p>
 <p>If you use your own fonts, the font must have a glyph for the desired character. Furthermore the font must be available on the machine where the PDF is viewed or it must have been embedded in the PDF file. See <a href="1.1/fonts.html">embedding fonts</a>.</p>
-<p>For most symbols, it is better to select the symbol font explicitely, for example in order to get the symbol for the mathematical empty set, write:
-<fo:inline font-family="Symbol">&#x2205;</fo:inline>
-The "#" shows up if the selected font does not define a glyph for the required character, for example if you try:
-<fo:inline font-family="Helvetica">&#x2205;</fo:inline></p>
+<p>For most symbols, it is better to select the symbol font explicitely, for example in order to get the symbol for the mathematical empty set, write:</p>
+<div class="codehilite"><pre><span class="nt">&lt;fo:inline</span> <span class="na">font-family=</span><span class="s">&quot;Symbol&quot;</span><span class="nt">&gt;</span><span class="ni">&amp;#x2205;</span><span class="nt">&lt;/fo:inline&gt;</span>
+</pre></div>
+
+
+<p>The "<code>#</code>" shows up if the selected font does not define a glyph for the required character, for example if you try:</p>
+<div class="codehilite"><pre><span class="nt">&lt;fo:inline</span> <span class="na">font-family=</span><span class="s">&quot;Helvetica&quot;</span><span class="nt">&gt;</span><span class="ni">&amp;#x2205;</span><span class="nt">&lt;/fo:inline&gt;</span>
+</pre></div>
+
+
 <h3 id="pdf-postprocess">6.3. What tools are available for post-processing my PDF document?</h3>
 <p>See <a href="1.1/output.html#pdf-postprocess">PDF Post-processing</a>.</p>
 <h3 id="pdf-security">6.4. How do I add security features (encryption, disable printing) to my PDF document?</h3>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org