> On Sunday 26 January 2003 03:47 pm, Jeff Garland wrote: > > One thing, however, is that the image source files are not copied > > to the destination. So we will either have to make sure all > > references are to the source location or add something to the > > build steps to copy the image files. > > > > Jeff > > It's probably best to make sure references go to the appropriate source > location, so that we don't end up with two copies of every image. Either we
Makes sense. > could specify that the image filenames are relative to $(BOOST_ROOT) and have > the BoostBook XSL put in the appropriate relative path or we could require > that all images be in libs/<library-name>/doc_src/images and include a > <libimagedata> element that looks there for images. Probably either would be fine although I'm not sure I follow the need for libimagedata? And perhaps we should just leave them in the <lib-name>/doc/images since that is the target destination. This will allow for simpler extraction of docs (we don't have to reach into a doc_src directory). I'm assuming we will still be checking-in the derived html documentation at this location anyway so we could just leave the images here. Jeff ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
