[Bug 53820] New: Wishlist: Image callouts in Docbook that actually work

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53820

          Priority: P2
            Bug ID: 53820
          Assignee: fop-dev@xmlgraphics.apache.org
           Summary: Wishlist: Image callouts in Docbook that actually work
          Severity: enhancement
    Classification: Unclassified
                OS: All
          Reporter: jan@brogger.no
          Hardware: All
            Status: NEW
           Version: 1.0
         Component: general
           Product: Fop

I'm not sure this is a FOP problem, or if it is the Docbook stylesheets that is
the problem. I suspect that FOP would need to do the work anyways.

The image callout tag in Docbook (any version) is not useful. When writing user
manuals for software, a not insignificant part of the work is creating
screenshots and marking parts of the screen. If the screens could be "tagged"
with callouts in a structured manner such as Docbook, then the workload would
be significantly reduced. People use all sorts of horrible solutions such as
doing it in Word, Powerpoint, or many different programs. 

One authoritative source has a work-intensive workaround. 
http://norman.walsh.name/2006/06/10/imageobjectco

This documents the tag:
http://www.sagehill.net/docbookxsl/Imagemaps.html

Current status with FOP:
Callouts are not rendered on top of images
Callouts are rendered in a calloutlist, below the figure (using standard
stylesheets).

Expected behavior:
Given the following input:
    <figure>
      <title>The main screen</title>
      <mediaobject>
        <imageobjectco>
          <areaspec units="calspair">
            <area coords="0, 0 1000, 1000" xml:id="firstcallout"/>
          </areaspec>
          <imageobject>
            <imagedata fileref="screenshots/mainscreen.jpg"/>
          </imageobject>
          <calloutlist>
            <callout arearefs="firstcallout">
              <para>A first callout</para>
            </callout>
          </calloutlist>
        </imageobjectco>
      </mediaobject>
    </figure>

FOP should ideally produce a PDF file with a figure looks like "mainscreen.jpg"
but is actually "mainscreen.jpg" merged with a "1.svg" file at the coordinates
(callout number 1).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53820] Wishlist: Image callouts in Docbook that actually work

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53820

--- Comment #2 from Vincent Hennebert <vh...@gmail.com> ---
(In reply to comment #1)
> FOP != DocBook; if you can express your enhancement request in terms of
> XSL-FO 1.1 [1] features or the future looking XSL-FO 2.0 requirements [2],
> then feel free to file a new enhancement bug
> 
> [1] http://www.w3.org/TR/2006/REC-xsl11-20061205/
> [2] http://www.w3.org/TR/xslfo20-req/

A little less abrupt answer would be preferable. User feedback is precious and
we wouldn't want to scare them off by responding bluntly.

Jan, please describe your issue on the fop-users mailing list:
http://xmlgraphics.apache.org/fop/dev/index.html#mail-fop-dev (Bugzilla is used
to report identified bugs.)
Like Glenn send, your will have to provide us with an XSL-FO file (the result
of the transformation of your source DocBook file by the DocBook stylesheets),
as this is what we are working with. Ideally you would make it as small as
possible.

That said, you may want to try the docbook-apps mailing list first, as it might
just be a matter of customizing the DocBook stylesheets.
http://wiki.docbook.org/DocBookAppsMailingList

Thanks,
Vincent

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 53820] Wishlist: Image callouts in Docbook that actually work

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53820

Glenn Adams <ga...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Glenn Adams <ga...@apache.org> ---
FOP != DocBook; if you can express your enhancement request in terms of XSL-FO
1.1 [1] features or the future looking XSL-FO 2.0 requirements [2], then feel
free to file a new enhancement bug

[1] http://www.w3.org/TR/2006/REC-xsl11-20061205/
[2] http://www.w3.org/TR/xslfo20-req/

-- 
You are receiving this mail because:
You are the assignee for the bug.