From 1a94d018d0786e0d74d02b26e49ffcb636c89c20 Mon Sep 17 00:00:00 2001 From: William Victor Mote Date: Wed, 14 May 2003 17:53:56 +0000 Subject: [PATCH] Cleanup BMP and TIFF documentation. Content credited to Robert P. J. Day and Jeremias Maerki. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196428 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/graphics.xml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/src/documentation/content/xdocs/graphics.xml b/src/documentation/content/xdocs/graphics.xml index e7de58e0c..c2386d9aa 100644 --- a/src/documentation/content/xdocs/graphics.xml +++ b/src/documentation/content/xdocs/graphics.xml @@ -20,7 +20,7 @@ BMP (Microsoft Windows Bitmap) bitmap - JIMI or JAI + FOP native CUR @@ -93,9 +93,9 @@ JIMI - TIFF (Tag Image Format File) + TIFF (Tag Image Format File) bitmap - JIMI or JAI + FOP native or JAI, depending on the subformat. See TIFF for more details.(JIMI also supports TIFF, but this has not been implemented within FOP). XBM (X BitMap) @@ -277,6 +277,10 @@ into a raster graphic are not drawn properly in PDF. The image is opaque. +
+ TIFF +

TIFF images with JPEG or CCITT content are passed through by FOP natively. Other TIFF subformats are handled by JAI.

+
Graphics Resolution

Some bitmapped image file formats store a dots-per-inch (dpi) or other resolution value. Since PDF and most output formats do not have a concept of resolution, but only of absolute image units (i.e. pixels) FOP ignores the resolution values as well. Instead, FOP uses the dimensions of the image as specified in the fo:external-graphic element to render the image:

-- 2.39.5