On Fri, Aug 24, 2012 at 9:09 PM, Stefan Hinz <stefan.h...@oracle.com> wrote:
> > So, quite apparently, note.svg is inserted for a DocBook <note>. (I've > confirmed for other instances of note.svg in the FO file.) > > But when searching the DocBook XSL style sheets (local copy) for note.svg, > all I get is this: > > 2005-01-05 Jirka Kosek <ko...@users.sourceforge.net> > > * caution.svg, important.svg, note.svg, tip.svg, warning.svg: > New file. > > No clue as to how the file gets inserted into the FO. :-( > > Searching e.g. the 1.77.1 DocBook XSL style sheets for note.svg gives me > this: > > docbook-xsl-1.77.1/images/**colorsvg/note.svg > docbook-xsl-1.77.1/images/**note.svg > > Still no clue why (and how) note.svg is referenced in the FO, but at least > it's an existing file, although FOP seems to expect it in a different > location (../common/images), thus the error. > > What do you think? Is this a DocBook XSL bug (in which case I'll bring it > up on the DocBook mailing list), or could FOP be doing something wrong? > GIGO applies; the problem is in the XSLT you are using, not FOP; as I stated, the real input to FOP is the FO document, and your XSLT is feeding it a bogus URL location, so you need to debug the XML -> FO (via XSLT) process, not the FOP (Formatting) process
