xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840201 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/trunk/graphics.html
Date Fri, 30 Nov 2012 16:09:24 GMT
Author: buildbot
Date: Fri Nov 30 16:09:23 2012
New Revision: 840201

Staging update by buildbot for xmlgraphics

    websites/staging/xmlgraphics/trunk/content/   (props changed)

Propchange: websites/staging/xmlgraphics/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 30 16:09:23 2012
@@ -1 +1 @@

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/graphics.html
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/graphics.html Fri Nov 30 16:09:23
@@ -358,72 +358,18 @@ $(document).ready(function () {
 <p>The actual <a href="http://xmlgraphics.apache.org/commons/image-loader.html">image
loading framework</a> does not reside in Apache FOP, but in <a href="http://xmlgraphics.apache.org/commons/">XML
Graphics Commons</a> .</p>
 <h2 id="overview-of-graphics-support-wzxhzdk5wzxhzdk6">Overview of Graphics Support
<a id="support-overview"></a></h2>
 <p>The table below summarizes the <em>theoretical</em> support for graphical
formats within FOP. In other words, within the constraints of the limitations listed here,
these formats <em>should</em> work. However, many of them have not been tested,
and there may be limitations that have not yet been discovered or documented. The packages
needed to support some formats are not included in the FOP distribution and must be installed
separately. Follow the links in the "Support Through" columns for more details.</p>
-<th>Support Through</th>
-<td><a href="#native">Apache FOP (native)</a></td>
-<td><a href="#batik">Apache Batik</a></td>
-<td><a href="#imageio">Image I/O</a></td>
-<td><a href="#bmp">BMP</a> (Microsoft Windows Bitmap)</td>
-<td><a href="#emf">EMF</a> (Windows Enhanced Metafile)</td>
-<td>vector (with embedded bitmaps)</td>
-<td><a href="#eps">EPS</a> (Encapsulated PostScript)</td>
-<td>metafile (both bitmap and vector), most frequently used for vector drawings</td>
-<td>GIF (Graphics Interchange Format)</td>
-<td><a href="#jpeg">JPEG</a> (Joint Photographic Experts Group)</td>
-<td><a href="#png">PNG</a> (Portable Network Graphic)</td>
-<td><a href="#svg">SVG</a> (Scalable Vector Graphics)</td>
-<td>vector (with embedded bitmaps)</td>
-<td><a href="#tiff">TIFF</a> (Tag Image Format File)</td>
-<td><a href="#wmf">WMF</a> (Windows Metafile)</td>
-<td>vector (with embedded bitmaps)</td>
+<p>| Format | Type | Support Through |
+|  <a href="#native">Apache FOP (native)</a>  |  <a href="#batik">Apache
Batik</a>  |  <a href="#imageio">Image I/O</a>  |
+|  <a href="#bmp">BMP</a> (Microsoft Windows Bitmap) | bitmap |  |  | X [1] |
+|  <a href="#emf">EMF</a> (Windows Enhanced Metafile) | vector (with embedded
bitmaps) | (X) |  |  |
+|  <a href="#eps">EPS</a> (Encapsulated PostScript) | metafile (both bitmap and
vector), most frequently used for vector drawings | (X) |  |  |
+| GIF (Graphics Interchange Format) | bitmap |  |  | X |
+|  <a href="#jpeg">JPEG</a> (Joint Photographic Experts Group) | bitmap | (X)
|  | X |
+|  <a href="#png">PNG</a> (Portable Network Graphic) | bitmap |  |  | X |
+|  <a href="#svg">SVG</a> (Scalable Vector Graphics) | vector (with embedded
bitmaps) |  | X |  |
+|  <a href="#tiff">TIFF</a> (Tag Image Format File) | bitmap | (X) |  | X [1]
+|  <a href="#wmf">WMF</a> (Windows Metafile) | vector (with embedded bitmaps)
|  | (X) |  |</p>
@@ -580,24 +526,24 @@ Batik must be run in a graphical environ
 <h3 id="png-wzxhzdk35wzxhzdk36">PNG <a id="png"></a></h3>
 <p>PNG images are supported through an Image&nbsp;I/O codec. Transparency is supported
but not guaranteed to work with every output format.</p>
 <h3 id="svg-wzxhzdk38wzxhzdk39">SVG <a id="svg"></a></h3>
-<h4 id="introduction-wzxhzdk40wzxhzdk41">Introduction ## <a id="svg-intro"></a></h4>
+<h4 id="introductionwzxhzdk40wzxhzdk41">Introduction<a id="svg-intro"></a></h4>
 <p>FOP uses <a href="#batik">Apache Batik</a> for SVG support. This format
can be handled as an <code>fo:instream-foreign-object</code> or in a separate
file referenced with <code>fo:external-graphic</code> .
 Batik's SVG Rasterizer utility may also be used to convert standalone SVG documents into
PDF. For more information please see the <a href="http://xmlgraphics.apache.org/batik/svgrasterizer.html">SVG
Rasterizer documentation</a> on the Batik site.</p>
-<h3 id="placing-svg-graphics-into-pdf-wzxhzdk42wzxhzdk43">Placing SVG Graphics into
PDF ## <a id="svg-pdf-graphics"></a></h3>
+<h3 id="placing-svg-graphics-into-pdfwzxhzdk42wzxhzdk43">Placing SVG Graphics into
PDF<a id="svg-pdf-graphics"></a></h3>
 <p>The SVG is rendered into PDF by using PDF commands to draw and fill lines and curves.
This means that the graphical objects created with this remain as vector graphics. The same
applies to PostScript output. For other output formats the SVG graphic may be converted to
a bitmap image.</p>
 <p>There are a number of SVG things that cannot be converted directly into PDF. Parts
of the graphic such as effects, patterns and images are inserted into the PDF as a raster
graphic. The resolution of these raster images can be controlled through the "target resolution"
setting in the <a href="configuration.html">configuration</a> .</p>
 <p>Currently transparency is limited in PDF so some SVG images that contain effects
or graphics with transparent areas may not be displayed correctly.</p>
-<h4 id="placing-svg-text-into-pdf-and-postscript-wzxhzdk44wzxhzdk45">Placing SVG Text
into PDF and PostScript ## <a id="svg-pdf-text"></a></h4>
+<h4 id="placing-svg-text-into-pdf-and-postscriptwzxhzdk44wzxhzdk45">Placing SVG Text
into PDF and PostScript<a id="svg-pdf-text"></a></h4>
 <p>If possible, Batik will use normal PDF or PostScript text when inserting text. It
does this by checking if the text can be drawn normally and the font is supported. This example
svg <a href="../dev/svg/text.svg">text.svg</a> / <a href="../dev/svg/text.pdf">text.pdf</a>
/ <a href="../dev/svg/text.png">text.png</a> shows how various types and effects
with text are handled. Note that SVG font support is not yet implemented. Furthermore, text
handling in PostScript output is inferior to PDF output - more text will be painted as shapes
in PS than in PDF.</p>
 <p>When there's no support to paint text using native text operations, text is converted
and drawn as a set of shapes by Batik, using the stroking text painter. This means that a
typical character will have about 10 curves (each curve consists of at least 20 characters).
This can make the output files large and when it is viewed the viewer may not normally draw
those fine curves very well (In Adobe Acrobat, turning on "Smooth Line Art" in the preferences
will fix this). Copy/paste functionality will not be supported in this case. If the text is
inserted into the output file using the inbuilt text commands it will use a single character.</p>
 <p>Note that because SVG text can be rendered as either text or a vector graphic, you
may need to consider settings in your viewer for both. The Acrobat viewer has both "smooth
line art" and "smooth text" settings that may need to be set for SVG images to be displayed
nicely on your screen (see Edit / Preferences / Display). This setting will not affect the
printing of your document, which should be OK in any case, but will only affect the quality
of the screen display.</p>
-<h4 id="font-selection-notes-wzxhzdk46wzxhzdk47">Font selection notes ## <a id="svg-font-selection"></a></h4>
+<h4 id="font-selection-noteswzxhzdk46wzxhzdk47">Font selection notes<a id="svg-font-selection"></a></h4>
 <p>Apache Batik uses the AWT/Java2D subsystem as font source while FOP has its own
font subsystem. Great care has been taken that font selection does the best possible choices.
But it must be noted when creating PDF or PostScript that a font used in SVG graphics needs
to be registered with the operating system as well as in FOP's configuration. By using FOP's
font auto-detection, you simply have to install the font in the operating system and not care
about anything else. This is less of an issue if you create formats like TIFFs, PNGs or PCL
because in these cases SVG graphics are usually rendered to bitmaps which means that on both
sides (Batik and FOP), AWT/Java2D is used as the single font source.</p>
 <p>Whenever an SVG is converted into a PDF or PostScript file, the font that has been
used inside Batik has to be mapped to a font used by the actual output format. Features like
font substitution in FOP may need to be taken into account but can also be an advantage when
working around font mapping issues. Like for XSL-FO content, you'll get a warning if a particular
font could not be found and had to be substituted, or if a particular glyph is missing in
a font.</p>
-<h4 id="scaling-wzxhzdk48wzxhzdk49">Scaling ## <a id="svg-scaling"></a></h4>
+<h4 id="scalingwzxhzdk48wzxhzdk49">Scaling<a id="svg-scaling"></a></h4>
 <p>Currently, SVG images are rendered with the dimensions specified <em>in the
SVG file</em> , within the viewport specified in the fo:external-graphic element. For
everything to work properly, the two should be equal. The SVG standard leaves this issue as
an implementation detail. Additional scaling options are available through XSL-FO means.</p>
 <p>If you use pixels to specify the size of an SVG graphic the "source resolution"
setting in the <a href="configuration.html">configuration</a> will be used to
determine the size of a pixel. The use of pixels to specify sizes is discouraged as they may
be interpreted differently in different environments.</p>
-<h4 id="known-problems-wzxhzdk50wzxhzdk51">Known Problems ## <a id="svg-problems"></a></h4>
+<h4 id="known-problemswzxhzdk50wzxhzdk51">Known Problems<a id="svg-problems"></a></h4>
 <p>Soft mask transparency is combined with white so that it looks better on PDF 1.3
viewers but this causes the soft mask to be slightly lighter or darker on PDF 1.4 viewers.</p>

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

View raw message