Philippe Nobili wrote: > Many thanks, I think we'll implement the last method, since we have > already a customized xslMenu.incl file. > By the way, the reason why we had to change the xslMenu.incl file is > because of the following problem (maybe we did not understand how to fix > this properly...): > > When we convert our XML file, the resources are copied to the > destination location something like this in xslMenu.incl: > > <copyProcessResources resources="xsl/images/draft.png" to="images" /> > > Unfortunately, when we use graphical admonitions (admon.graphics set to > 1), the corresponding icons are missing in output destination (only > draft.png is present). So we had to modify the statement to something like: > > <copyProcessResources resources="@xsl/images/default_images.list" > to="images" /> > > where default_images.list lists the icons we need for admonitions. > > I suppose it would not be difficult to fix cleanly this problem in > XMLMind (if you think it is one), and automatically copy all internal > graphics to the destination directory ? Maybe this needs to be a bit > more sophisticated from what we did, as taking into account the > admon.graphics and admon.graphics.extension parameters to determine > which graphics have to be copied etc etc ?? >
This is simply an omission. We'll replace: <copyProcessResources resources="xsl/images/draft.png" to="images" /> by something like: <copyProcessResources resources="xsl/images/png_images.list" to="images"/> in next release. (We'll use SVG files for PDF and PostScript because XEP does not really support PNG files having a transparent background). Note that there is currently no way to make the copyProcessResources smarter e.g. copy caution.png, important.png, etc, but only if admon.graphics=1; copy callouts/1.png, 2.png, etc, but only if callout.graphics=1; etc.
