From 79a1d0325d3ec281afc35eada11640e97579f412 Mon Sep 17 00:00:00 2001
From: William Victor Mote
Date: Tue, 22 Apr 2003 19:22:55 +0000
Subject: [PATCH] Add faq for graphics resolution. Move other graphics-related
faqs together.
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196323 13f79535-47bb-0310-9956-ffa450edef68
---
src/documentation/content/xdocs/faq.xml | 78 +++++++++++++------------
1 file changed, 42 insertions(+), 36 deletions(-)
diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml
index 6f4942856..6057cbed9 100644
--- a/src/documentation/content/xdocs/faq.xml
+++ b/src/documentation/content/xdocs/faq.xml
@@ -369,12 +369,54 @@
+
+ A graphic is not displayed.
+
+
+ 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&paste the source URL from the fo:external-graphic into the
+ Location field of a browser on the machine where the FOP
+ process will be running.
+
+
+ Several other possibilities:
+
+
+
+ The graphic is too large to fit into the intended space.
+
+
+ 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)
+
+
+ Something else obscures the graphic, for example stuff from a
+ static content (very rare, but has happened).
+
+
+
+
+ My graphical images do not work properly.
See Graphical Formats.
+
+ Why is my graphic rendered at a different resolution than it was created?
+
+
See Graphics Resolution.
+
+ Keep-with-next, keep-with-previous, keep-together
don't work.
@@ -473,42 +515,6 @@
-
- A graphic is not displayed.
-
-
- 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&paste the source URL from the fo:external-graphic into the
- Location field of a browser on the machine where the FOP
- process will be running.
-
-
- Several other possibilities:
-
-
-
- The graphic is too large to fit into the intended space.
-
-
- 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)
-
-
- Something else obscures the graphic, for example stuff from a
- static content (very rare, but has happened).
-