...
- Create the image file and add to the images directory.
Use oXygen to link to the image file and you should be able to navigate to the image file in the GUI and the path will be generated for you. Image paths should be relative, i.e. "../images/image_name.png" and use underscores instead of spaces since they are more web friendly.
Make sure the image is sized properly by building the webhelp and PDF versions and ensuring that they show up ok. Improperly sized images can look pretty bad, especially in the PDF output. Tools like Gimp are free and can be used to do the resizing.
Image files are inserted this ways into docbooks.
Code Block <inlinemediaobject><alt>example1</alt><imageobject><imagedata fileref="../images/EDL_Guide/example1.png" width="100%"/>
-OR-
Code Block <inlinemediaobject><alt>example1</alt><imageobject><imagedata fileref="../images/EDL_Guide/example1.png"/>
Screenshots are labeled as such:
Code Block <para> <screenshot> <mediaobject> <alt>E-Resource Note Tab</alt> <imageobject> <imagedata fileref="../images/eresource-42.png" width="100%"/> </imageobject> </mediaobject> </screenshot> </para>
Again, if they are small enough, do not include the "width="100%"
FYI: The alt tag is added for accessibility. In the webhelp and HTML outputs, the tag will also be displayed in the mouse-over.
Creating Hyperlinks
In DocBook 5, the preference is to have xlinks for hyperlinks. If you use the oXygen GUI (author view) to add the link, you'll need to right-click on the link and add the xlink:href property with the url of your link as the value.
...