Dave, I do something similar also. For HTML generation, I make sure all images (including Docbook images) are in one place. This makes Saxon complain about not seeing the images, but I resolve that afterwards by copying the images to the publishing image directory.
However, I have a lot of images in my directories that may not only be for HTML, because I also produce the FO/PDF and MSHELP docs. Since I don't want to copy the "whole mess" I run an XSL template on my XML books to output a batch file with the copying instructions as to which images are actually needed and leaving the rest of the "mess" behind. I also keep the filespaths in my XML relative which make portability a bit easier. Regards, Dean Nelson In a message dated 05/14/09 07:30:20 Pacific Daylight Time, [email protected] writes: > Which is my solution too Eric! No, I'm not thinking its > the smart way to do it! I now have this set of > graphics all over my disk and website! - For a website, set the user parameters "navig.graphics.path", "admon.graphics.path" (and all other image paths) to either "/graphics/" or "http://graphics.example.com/";. Put all your graphics in that dir. - For your local disk, set "navig.graphics.path", "admon.graphics.path" (and all other image paths) to "/path/to/my/graphics" (or "C:\Path\To\My\Graphics"?). Put all your graphics in that dir. Personally, I just use softlinks for the images dir, but I'm not sure whether these are available on your platform. cheers, Remko --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
