In response to your questions on graphics:
This is a bit of a headache. There are four ways to tag graphics:
- relative URI in an unparsed entity (using entityref)
- absolute URI in an unparsed entity
- relative URI in the fileref attribute
- absolute URI in the fileref attribute
In the past, we've always used the second form because we felt it left the
least room for error. However, I'm currently working on enabling all of the
other forms. I've written an extension function for Saxon that will find
the source graphic and copy it to the desired destination as part of the
build process. This makes my life much easier in this respect. (If
anybody's interested, I can work on posting it here in the next little bit.)
Our directory structure looks roughly like this:
build
-- product1
-- graphics
-- product2
-- graphics
xmlsource
-- product1
-- book1
-- book2
-- book3
-- allgraphics
-- product2
--book1
--book2
--book3
...
--book26
--allgraphics
This is a simplification of something that has grown very complicated over
time and will be very difficult to take back to a more simplistic and
workable form. Basically, I would suggest the following directory structure
build
-- product1
-- graphics
-- product2
-- graphics
xmlsource
--product1
-- book1
-- book1graphics
-- book2
-- book2graphics
-- product1graphics
--product2
-- book1
--book1graphics
--book2
--book2graphics
...
--book26
--book26graphcis
--product2graphics
--sharedgraphics
Jeff
