docbook-apps

  • 1.  SEVERE: Image not found

    Posted 08-24-2012 13:23
    Hi guys,

    I asked about a FOP problem on the fop-users list, but it turned out to
    be not a FOP problem, but rather an issue with the DocBook style sheets,
    thus bringing it up on this list.

    The issue: When creating PDF, I get lots of warnings like this:

    SEVERE: Image not found. URI: ../common/images/note.svg. ...

    This is not severe at all (the PDF builds fine, no issues in the layout,
    etc.), but the warnings clutter up the output, which makes it hard to
    identify real issues like overflow problems.

    So I created FO to see where note.svg would show up. Here's a relevant
    snippet:

    <fo:block><fo:external-graphic width="auto" height="auto"
    content-width="36pt"
    src="url(../common/images/note.svg)"/></fo:block></fo:list-item-label><fo:list-item-body

    start-indent="body-start()"><fo:block space-before.minimum="0em"
    space-before.optimum="0em" space-before.maximum="0em"
    font-family="Helvetica,Verdana,Arial,Sans Serif" font-size="10pt"
    font-weight="bold" margin-left="0.25in" margin-right="0.25in"
    border-left="5pt solid black" padding-left="0.1in" hyphenate="false"
    keep-with-next.within-column="always">Note</fo:block><fo:block
    space-before.minimum="0em" space-before.optimum="0em"
    space-before.maximum="0em" margin-left="0.25in" margin-right="0.25in"
    border-left="5px solid black" padding-left="0.1in"><fo:block
    space-before.optimum="1em" space-before.minimum="0.8em"
    space-before.maximum="1.2em">
    The logic of the previous example also applies for a
    relation such as this one:

    In DocBook, this would be:

    <note>
    <para>
    The logic of the previous example also applies for a
    relation such as this one:

    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 <kosek@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.

    This looks like a bug in the DocBook XSL style sheets to me, but maybe
    it's not. In any case, how could I work around this issue, so that the
    warnings won't show up any more? (I could probably copy note.svg and
    friends to a ../common/images/ folder for each of our docs, but I'd
    rather avoid that.)

    Thanks in advance for any pointers!

    Cheers,

    Stefan

    > For example, use
    >
    > fop -xml test.xml -xsl test.xsl -foout test.fo.xml
    >
    > On Wed, Aug 15, 2012 at 7:19 AM, Stefan Hinz <stefan.hinz@oracle.com
    > <mailto:stefan.hinz@oracle.com>> wrote:
    >
    > I've googled for the annoying messages FOP 1.0 spits out, and found
    > quite a few complaints, but no resolution. So here are my questions
    > to you:
    >
    > When converting DocBook XML to PDF, using xsltproc and the DocBook
    > XSL style sheets version 1.77.1 (it's not specific to that version,
    > just saying), I get a gazillion warnings like this:
    >
    > SEVERE: Image not found. URI: ../common/images/note.svg. ...
    >
    > They're just warnings, but they clutter up the output so that it's
    > hard to spot real problems such as overflow issues.
    >
    > (1) Any idea what causes those warnings? We're not using SVG images
    > at all, just PNG files. Particularly, we're not using files in
    > ../common/images (there's no such directory for any of our books).
    >
    > (2) Assuming it's some FOP-internal thing (a bug?) that cannot be
    > fixed on our end, is there a workaround to stop FOP from issuing
    > those warnings?
    >
    > (3) How would I find out the exact FOP version I'm using? (I'm
    > thinking maybe it's a bug that would be fixed by upgrading to a
    > newer version.) When running "fop --version" it just reports "1.0".
    >
    > Thanks much for any pointers!
    >
    > --
    > Cheers,
    >
    > Stefan Hinz <stefan.hinz@oracle.com
    > <mailto:stefan.hinz@oracle.com>>, MySQL Documentation Manager
    >
    > Phone: +49-30-82702940 <tel:%2B49-30-82702940>, Fax: +49-30-82702941
    > <tel:%2B49-30-82702941>, http://dev.mysql.com/doc
    >
    > ORACLE Deutschland B.V.& Co. KG
    > Registered Office: Riesstr. 25, 80992 Muenchen, Germany
    > Commercial Register: Local Court Of Munich, HRA 95603
    > Managing Director: Jürgen Kunz
    >
    > General Partner: ORACLE Deutschland Verwaltung B.V.
    > Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
    > Register Of Chamber Of Commerce: Midden-Niederlande, No. 30143697
    > Managing Directors: Alexander van der Ven, Astrid Kepper, Val Maher
    >
    > ------------------------------__------------------------------__---------
    > To unsubscribe, e-mail:
    > fop-users-unsubscribe@__xmlgraphics.apache.org
    > <mailto:fop-users-unsubscribe@xmlgraphics.apache.org>
    > For additional commands, e-mail:
    > fop-users-help@xmlgraphics.__apache.org
    > <mailto:fop-users-help@xmlgraphics.apache.org>
    >
    >


    --
    Cheers,

    Stefan Hinz <stefan.hinz@oracle.com>, MySQL Documentation Manager

    Phone: +49-30-82702940, Fax: +49-30-82702941, http://dev.mysql.com/doc

    ORACLE Deutschland B.V.& Co. KG
    Registered Office: Riesstr. 25, 80992 Muenchen, Germany
    Commercial Register: Local Court Of Munich, HRA 95603
    Managing Director: Jürgen Kunz

    General Partner: ORACLE Deutschland Verwaltung B.V.
    Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
    Register Of Chamber Of Commerce: Midden-Niederlande, No. 30143697
    Managing Directors: Alexander van der Ven, Astrid Kepper, Val Maher