Description of problem: I have been working of late to see how feasible it is to build documentation from the openstack-manuals project using Publican, allowing us to single source while working with the upstream community. At this time I am looking at using a pre-build script to perform some transformations on the XML to allow this but some of these seem like they should/could be unnecessary. One of the minor differences I have come across is that they use a "figures" directory instead of "images". This didn't seem like it would be a big problem but it appears that this directory doesn't make it into the build and therefore the output. When I build a book that has an image in the "en-US/figures" directory that is linked in from the XML I can see that the figures directory makes it as far as "tmp/en-US/xml_tmp/" but does not appear in "tmp/en-US/xml/" or the output formats. I would like to be able to use images regardless of sub-directory name/structure in the same way we can with XML. Note I recognize there is some benefit to knowing "all images are in the images directory" but at the same time in this case the same would be true, just s/images/figures/. I'm proposing a broader approach because obviously the next project someone looks at might use "pictures" or "pngs" or whatever. Version-Release number of selected component (if applicable): publican-3.1.3-1.fc17.noarch
Add a new parameter image_dir that acts like tmp_dir, defaults to 'images'.
HSS-QE has reviewed and declined this request. QE for this bug will be handled by IED.
Added img_dir parameter for publican.cfg. Updated docs. To ssh://git.fedorahosted.org/git/publican.git 9974a40..cc52af9 HEAD -> devel
Publican now allows for setting a custom image directory using an "image_dir" parameter in the configuration file. Verified in publican-3.1.5-0.fc17.t62.noarch.
The fix for this bug has been shipped in publican 3.2.0