UDO enables you to include images into your destination format if it supports images like ST-Guide, LaTeX, HTML and Windows Help. This chapter explains how to include images into a destination file and what destination commands UDO generates.
To display an image you can use the !image command. You have to add the name of the image without suffix and an optional image title.
To display images right inside the text you can use the placeholder (!img ..) when converting into Windows Help or HTML. The other formats don't allow to use images inside the text or it is so difficult that UDO can't automatize it.
Since Release 6 images will not be centred in all cases. To display a centred image you have to insert the !image command into a center environment. To display a right justified image you have to insert the !image command inside a flushright environment. In all other cases images will be displayed left justified.
Example: !image tiger A tiger
UDO opens the file tiger.img and reads the size of this image. A special ST-Guide command called @limage is generated and the needed parameters are calculated due to the information of the GEM image header.
If you want to display a subtitle add it right after the name of the image file. This subtitle will look like "(Figure x: A tiger)".
If you are using Lindner-TeX and you want to include a GEM image into your DVI file you have to add !tex_lindner to your preamble.
UDO replaces the tool called IMGTOTEX that is part of Lindner-TeX. UDO has all functions of this tool built in.
To set the size of an image you have to use the !tex_dpi command. An example:
!tex_dpi 100 !image tiger A GEM image
UDO reads in the header of tiger.img, calculates its size and adjusts the header to 100 dpi. In the destination file a TeX macro will be generated that includes this image and displays it with 100 dpi.
Please note: Using 100 dpi screenshots are displayed in the original screen size on my HP DeskJet 510. !tex_dpi can be used before any image. If you are using an image more than once you shouldn't try to display it in different resolutions. Use a copy of your image instead and display the original one with the first and the copy with the second resolution.
If you are using CS-TeX or MultiTeX and you want to include a GEM image into your DVI file you have to add !tex_strunk to your preamble.
Because the drivers of CS-TeX support the macros of Lindner-TeX the same is done here as in the upper section.
If you are using emTeX and you want to include an MSP image to your DVI file you have to add !tex_emtex to your preamble. Furthermore you have to set the resolution of an image via !tex_dpi.
The macros for emTeX are generated according to the information of dvidrv.doc of emTeX.
In first place UDO tries to read in the header of tiger.msp when reading the command !image tiger A tiger. If UDO doesn't find tiger.msp it will try to find tiger.pcx.
An example shows what kind of macro UDO generates for emTeX. `w' and `h' represent the width and height of the image:
\begin{figure}[htb]
\begin{...}
\begin{picture}(<w>,<h>)
\put(0,<h>){\special{em:graph tiger.msp}}
\end{picture}
\end{...}
\caption{A tiger}
\end{figure}
Please note: I use !tex_dpi 300 on my HP DeskJet 510 to display screenshots.
If you are using emTeX and you want to include a Paintbrush PCX to your DVI file you have to add !tex_emtex to your preamble. Furthermore you have to set the resolution of an image via !tex_dpi.
The macros for emTeX are generated according to the information of dvidrv.doc of emTeX.
In first place UDO tries to read in the header of tiger.msp when reading the command !image tiger A tiger. If UDO doesn't find tiger.msp it will try to find tiger.pcx.
An example shows what kind of macro UDO generates for emTeX. `w' and `h' represent the width and height of the image:
\begin{figure}[htb]
\begin{...}
\begin{picture}(<w>,<h>)
\put(0,<h>){\special{em:graph tiger.pcx}}
\end{picture}
\end{...}
\caption{A tiger}
\end{figure}
Note: In first place UDO tries to find an MSP image. If you are using images from Paintbrush PCX you can ignore the warning printed by UDO.
UDO can generate HTML commands to include a GIF. UDO doesn't check if the GIF is existing!
For HTML the second parameter of the !image command will be used as the alternative text. The command !image tiger A tiger will be converted into the following HTML commands:
<p align=...> <img src="tiger.gif" alt="(Figure 1: A tiger)"> </p><br>
If you don't set the title of this image UDO doesn't output an alternative text. The command !image tiger will be converted into this:
<p align=...> <img src="../gif/tiger.gif" alt=""> </p><br>
By default UDO expects that you want to display GIF's (see above). But it's possible to display any other kind of image format, too.
To tell UDO which suffix you want to use the next time you use the !image command you can use the command !html_img_suffix.
If the upper tiger isn't inside a GIF but inside a JPEG image you can insert the following command right before the !image command:
!html_img_suffix jpg
If the file is named tiger.jpeg instead of tiger.jpg use the following line:
!html_img_suffix jpeg
The setting is used for all following images. If you want to display a GIF next time you have to use !html_img_suffix gif before the next !image command is used.
UDO can generate commands for Windows Help to display Windows bitmaps (BMP). UDO doesn't check if a BMP is existing!
An image can be displayed with or without a subtitle. Windows Help centers the image in the help file.
UDO will then generate these commands:
{\qc \{bmc tiger.bmp\}}\par\pard
\par
{\qc (Figure 1: A tiger)}\par\pard
Please note: