From 450450ded82131c048c19e48f445d550c5965639 Mon Sep 17 00:00:00 2001 From: Vincent Hennebert Date: Tue, 22 Jan 2008 10:48:43 +0000 Subject: [PATCH] Fixed minor typos git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@614169 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/trunk/graphics.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/documentation/content/xdocs/trunk/graphics.xml b/src/documentation/content/xdocs/trunk/graphics.xml index b0ca327dd..7fc5c31e2 100644 --- a/src/documentation/content/xdocs/trunk/graphics.xml +++ b/src/documentation/content/xdocs/trunk/graphics.xml @@ -155,8 +155,8 @@

Not all image formats are supported for all output formats! For example, while you can use EPS (Encapsulated PostScript) files when you generate PostScript output, this format - will not be supported by any other output format. Here's an overview which image formats - are supported by which output format: + will not be supported by any other output format. Here's an overview of which image + formats are supported by which output format:

@@ -269,8 +269,8 @@ XML Graphics Commons Native

XML Graphics Commons supports a number - graphic file formats natively as basic functionality: all bitmap formats for which there - are Image I/O codecs available (JPEG, PNG, GIF, TIFF, etc.), EPS and EMF. + of graphic file formats natively as basic functionality: all bitmap formats for which + there are Image I/O codecs available (JPEG, PNG, GIF, TIFF, etc.), EPS and EMF.

@@ -501,7 +501,7 @@ Some bitmapped image file formats store a dots-per-inch (dpi) or other resolution values. FOP tries to use this resolution information whenever possible to determine the image's intrinsic size. This size is used during the layout process when it is not - superceeded by an explicit size on fo:external-graphic (content-width and content-height + superseded by an explicit size on fo:external-graphic (content-width and content-height properties).

-- 2.39.5