Hi John-
I'm not sure what's happening with your local printing and the different
path types, but unfortunately it gets more complicated when you get to
using PE for this.
PE has a special way of handling graphics, so that Editor can send local
graphic files with the document to the server and the server can do the
right thing with them. This is done using processing instructions, which
FOSI and Styler grok automatically, but which need a little extra work
with XSL-FO. Basically, you have to make sure your XSL-FO stylesheet
copies the PI's from the input to the FO
output in order for PE to be able to find the uploaded graphics and use
them. There will be one PI for each graphic, and it should be copied to
appear *immediately after* the corresponding <fo:external-graphic> in
the output tree.
The good thing about this is that you don't have to worry about graphic
paths at all-if Editor can find the graphics, it will insert all the
necessary info into the _graphic_data PI for you, and upload the actual
graphic when you publish on PE. In fact, when you use this approach, the
contents of the src attribute on <fo:external-graphic> are ignored in
favor of the info in the PI. (But, oddly, even though it's ignored, you
do have to have *some* value for the src attribute-if you just leave it
empty or omit it, the graphic won't appear.)
If you don't use the _graphic_data PI's (by turning the set pegraphicpi
option to "off", or by just not copying them in your XSL-FO stylesheet),
then you do have to worry about getting the path right for the
