Hi Lech,
Both figure and informalfigure accept mulitple mediaobject elements. The
difference,
of course, is that figure also requires a title and is numbered in output.
Each mediaobject can contain its own caption, or no caption, so that should
take care
of that requirement.
So you could use informalfigure to group multiple mediaobject elements, each with a
caption.
I don't know how you would do a parent-child relationship, though. Perhaps add
a role
attribute so the stylesheet can be customized somehow.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Lech Rzedzicki" <[email protected]>
To: "Docbook Apps" <[email protected]>
Cc: "docbook-developers" <[email protected]>
Sent: Friday, September 17, 2010 3:01 AM
Subject: [docbook-apps] How do you capture multiple illustrations?
Hi.
We want to capture groups of illustration using DB5 to represent an
illustrated book content.
For the individual illustration we will of course use <mediaobject>
but we're not sure how to group them nicely.
<figure> is sometimes ok, but other times the illustrations have
different caption, no captions or one illustration can be a "child" of
another (for instance it shows a zoomed in portion of the first
illustration).
What Docbook elements would you recommend for consistently
representing such varied scenarios?
Using section or a para to group them is a possible solution, but
doesn't introduce much semantic value into the markup and doesn't seem
very elegant to me.
Ideally I would want to reuse something that's already found in
Docbook Publishers SC, if not then from the full Docbook5, failing
that, we might have to come up with some custom elements or
attributes?
I really appreciate any feedback,
Lech
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]