Document EPS support & rework related FAQs a bit.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196369 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml
index eb6e0a691714543d59a1aade8dd34ab74b5dd7db..553281c3918a8b9271d0dd032db8e1d2840ab2c3 100644 (file)
--- a/src/documentation/content/xdocs/faq.xml
+++ b/src/documentation/content/xdocs/faq.xml
@@ -370,45 +370,31 @@
       </answer>
     </faq>
     <faq id="graphic-not-displayed">
-      <question>A graphic is not displayed.</question>
+      <question>Why is my graphic not rendered?</question>
       <answer>
-        <p>
-          The most common reason is that the file is not found because of an
-          empty or wrong baseDir setting, spelling errors in the file name, in
-          particular using the wrong case, or, if the image is retrieved over
-          HTTP, the image was not delivered because of security settings in the
-          server, missing cookies or other authorization information, or
-          because of server misconfigurations.  One way to check this is to
-          cut&amp;paste the source URL from the fo:external-graphic into the
-          Location field of a browser <strong>on the machine where the FOP
-          process will be running</strong>.
-        </p>
-        <p>
-          Several other possibilities:
-        </p>
+        <p>Most commonly, the external file is not being found by FOP.
+Check the following:</p>
         <ul>
-          <li>
-            The graphic is too large to fit into the intended space.
-          </li>
-          <li>
-            Some image format subclasses can't be handled, try to convert the
-            graphic to a format subclass known to work. (Sorry, no list of
-            formats known to work)
-          </li>
-          <li>
-            Something else obscures the graphic, for example stuff from a
-            static content (very rare, but has happened).
+          <li>Empty or wrong baseDir setting.</li>
+          <li>Spelling errors in the file name (including using the wrong case).</li>
+          <li>Security Problems (i.e. image was not delivered because FOP is not allowed to read the file).
+This is especially a problem if the external file is retrieved over HTTP.
+Possible issues include security settings on the server, server configuration, and missing cookies or other authorization information.
+Any easy way to check this is to cut&amp;paste the source URL from the fo:external-graphic into the Location field of a browser <strong>on the machine where the FOP process will be running</strong>.</li>
+        </ul>
+        <p>Other possibilities:</p>
+        <ul>
+          <li>The image format is not supported or not supported completely. See <link href="graphics.html">FOP Graphics Formats</link> for a list of supported formats and related issues.</li>
+          <li>The graphic may be too large to fit into the intended space.</li>
+          <li>There may be something (static content) that is obscuring the graphic. (This is very rare).
           </li>
         </ul>
-        <!-- p>
-          See also supported image formats.
-        </p -->
       </answer>
     </faq>
     <faq id="png-fails">
       <question>My graphical images do not work properly.</question>
       <answer>
-        <p>See <link href="graphics.html">Graphical Formats</link>.</p>
+        <p>See <link href="graphics.html">FOP Graphics Formats</link> for a list of supported formats and related issues.</p>
       </answer>
     </faq>
     <faq id="graphic-resolution">

diff --git a/src/documentation/content/xdocs/graphics.xml b/src/documentation/content/xdocs/graphics.xml
index 5f929d869a6db75729afcf41d3aa5cc2585cd535..809973071dd93160cac80ce3c0f474c888271f53 100644 (file)
--- a/src/documentation/content/xdocs/graphics.xml
+++ b/src/documentation/content/xdocs/graphics.xml
@@ -27,6 +27,11 @@
           <td>unknown</td>
           <td><link href="#jimi">JIMI</link></td>
         </tr>
+        <tr>
+          <td>EPS (Encapsulated PostScript)</td>
+          <td>metafile (both bitmap and vector), probably most frequently used for vector drawings</td>
+          <td>FOP native (limited support)</td>
+        </tr>
         <tr>
           <td>GIF (Graphics Interchange Format)</td>
           <td>bitmap</td>
@@ -132,6 +137,14 @@ JAI is much faster than JIMI, but is not available for all platforms. See <link
         <p>Current FOP distributions include a distribution of the Apache Software Foundation's <jump href="http://xml.apache.org/batik">Batik</jump> version 1.5beta4. No installation is required. Because Batik's API changes frequently, it is highly recommended that you use this version with FOP.</p>
       </section>
     </section>
+    <section id="eps">
+      <title>EPS</title>
+      <p>FOP provides support for two output targets:</p>
+      <ul>
+        <li>PostScript (full support).</li>
+        <li>PDF (partial support). FOP embeds the EPS file into the PDF, but currently does not do so completely correctly. PostScript devices (including ghostscript) will render the EPS correctly, but Acrobat Reader will not currently display it.</li>
+      </ul>
+    </section>
     <section id="jpeg">
       <title>JPEG</title>
       <p>Not all variants of JPEG are supported, especially those containing unusual color lookup tables and color profiles. If you have trouble with a JPEG image in FOP, try opening it with an image processing program (such as Photoshop or Gimp) and then saving it. Specifying 24-bit color output may also help.