Most images used in this demo are public domain, copyright-free, and come from the http://gimp-savvy.com/ photo archive. For a thorough description of how to specify images in DocBook documents, please consult the description of the imagedata element in DocBook: The Definitive Guide.

An inline image is represented by an inlinemediaboject/imageobject/imagedata element and a displayed image is represented by an mediaboject/imageobject/imagedata element. There are also the much simpler inlinegraphic and graphic elements but their use is more or less deprecated. The image files referenced by imagedata, inlinegraphic and graphic are specified using the Attribute tool by setting the fileref Specifying images using the entityref attribute of these elements is absolutely not supported by XMLmind XML Editor, as well as all the notation and non-parsed entity machinery inherited from SGML. attribute of these elements. However, it is much more convenient to double-click on the image or image placeholder and use the displayed dialog box or simply to drag and drop an image file on the image or image placeholder. The fileref attribute may also contain "data:" URLs. For example, the following fileref contains data:image/png;base64,...image data.

By default, images are displayed at their normal (intrinsic) size. The easiest way to resize an image is to specify the scale attribute of the imagedata element. The value of this attribute is a percentage of the normal size of the image. This is what we have done for the two fishes which are displayed inline above. Click on each of them and you'll see that we have specified scale=25% for the first one and scale=33 (% is implied) for the second one. It is also possible to directly specify the size of an image by setting the contentwidth and contentdepth of the imagedata element. Supported units are: pt (points — 1/72 of an inch) , cm (centimeters), mm (millimeters), in (inches), pc (picas — 1/6 of an inch), px (pixels), em (the unit here is the base font size, something close to 12pt). No unit means px (pixels). '%' is also supported and is a percentage of the normal size.

An image is drawn in a viewport. It is possible to explicitly specify the size of this viewport by setting the width and depth attributes of the imagedata element. In the image above, the viewport is much larger (5inx2in) than the image (10% of 779x704) and the image is aligned at the bottom/right of the viewport. This is specified by explicitly setting the valign and align attributes of the imagedata element to bottom and right (they default to middle and center). The most useful use of a viewport is to scale an image to fit the size of the viewport. This is done by removing the scale, contentwidth, contentdepth attributes if any, and setting the scalefit attribute of the imagedata element to 1.

The size of a viewport can be expressed as a percentage of the available area. This is very useful when images are added to table cells. Name Photo Duck Sea cow Now resize the window of XMLmind XML Editor and watch what happens. Note that specifying the depth of the imagedata element as a percentage is useless in XMLmind XML Editor which has no concept of page. Click on the above images and look at the Attribute tool to see how we have specified dynamic viewports for them.

Out of the box, XMLmind XML Editor supports all the image formats supported by the Java runtime: BMP, GIF, JPEG and PNG. In order to be able to really see the images below, you may need to download and install the Batik image toolkit plug-in using menu item Options Install Add-ons . Batik adds the support of SVG graphics.

MathML files A file having a .mml extension and containing presentation MathML is also considered to be a graphics file. If you install the "JEuclid" image toolkit plug-in (using Options Install Add-ons ), you should be able to see how the images below really look like. Gauss's law - differential equation is: . See also . Files containing TeX math A file having a .tex extension and containing TeX math is also considered to be a graphics file. If you install the "JLaTeXMath" image toolkit plug-in (using Options Install Add-ons ), you should be able to see how the image below really looks like. In the above equation, there is no need to add an alt child containing the equation written using the TeX notation: \[\hat{\beta} = \frac{\sum_{t=1}^n x_t y_t - \bar{y} \sum_{t=1}^n x_t} {\sum_{t=1}^n x^2_t - \bar{x}\sum_{t=1}^n x_t}\] Suffice to store this equation in a separate file having a ".tex" suffix (for the above equation, it is equations/eq2.tex) and XXE will automatically convert this file to SVG or PNG as needed. See also .

What if your images are stored using uncommon or proprietary formats? Aren't you tired of converting your images to GIF, JPEG or PNG in order to be able to use them in your documents? If you have a command line tool which can convert your images to GIF, JPEG or PNG, you can specify an image toolkit plug-in making use of such command line tool in just 5 minutes, without having to program. These declarative image toolkit plug-ins are specified in XML in XMLmind XML Editor configuration files. See XMLmind XML Editor - Configuration and Deployment, imageToolkit for details. To give external consultants and local gurus a quick start (authors are not expected to specify XMLmind XML Editor configurations), we have written a number of these declarative plug-ins: "Ghostscript" converts EPS and PDF graphics to PNG using the gs (gswin32c on Windows) command-line tool. "Inkscape WMF" converts WMF and EMF pictures to SVG or PNG using Inkscape. If you install these imageToolkit plug-ins properly These imageToolkit plug-ins are defined in XML file imagetoolkits.incl which is part of the add-on called "A sample customize.xxe". Please install this add-on using Options Install Add-ons and then refer to its documentation to learn how to put these plug-ins into use. See also XMLmind XML Editor - Configuration and Deployment, imageToolkit. , you should be able to see what the images below really look like.

If you are using XMLmind XML Editor Professional Edition, you can try converting this document to HTML, RTF, PostScript and PDF. In order to do this, you need to use the DocBook|Convert Document menu and specify a file name (a directory name for multi-page HTML) when prompted by the URL chooser dialog box. If you do this, what follows describes and analyzes what you'll see. XSL-FO Processor Output Format Image Geometry Image Formats N/A HTML Viewport not fully supported due to the limitations of HTML. All images in formats other than GIF, JPEG, PNG and SVG are automatically converted by the docb.toHTML (part of the DocBook configuration for XXE) process command to SVG or PNG.Of course, this requires the corresponding image toolkit plug-ins to have been properly installed. XMLmind XSL-FO Converter RTF, WordprocessingML (Word 2003+), Office Open XML (Word 2007+) and OpenDocument (OpenOffice / LibreOffice). XSL-FO specifications fully implemented. Supports SVG, thanks to Batik. Supports MathML, thanks to JEuclid. All images in formats other than GIF, JPEG, PNG and SVG are automatically converted by the docb.toRTF (part of the DocBook configuration for XXE) process command to SVG or PNG. Of course, this requires the corresponding image toolkit plug-ins to have been properly installed. Apache FOP PostScript Viewport is supported. FOP has a source-resolution configuration option. When run within XXE, the default value of source-resolution is 120DPI (like RenderX XEP) instead of default 72DPI. Supports SVG, including advanced features such as gradient fills thanks to Batik. Supports MathML, thanks to JEuclid. Natively supports EPS graphics when PostScript is generated. Does not support PDF graphics when PDF is generated. The resolution specified in PNG images is taken into account, which may give unexpected results. PDF RenderX XEP PostScript XSL-FO specifications fully implemented. Natively supports SVG but advanced features such as gradient fills are not yet implemented. Natively supports EPS graphics when PostScript is generated. Natively supports PDF graphics when PDF is generated. The resolution specified in PNG images is taken into account, which may give unexpected results. PDF