Hi Frank,
I think your analysis is correct. They should have different properties for the two
cases. Can you please file a bug report on the DocBook SourceForge site to get this
fixed? Thanks.
I'm not quite sure what values to assign for the inline case, though. The valign
attribute can take "top", "middle", and "bottom", but the relative-align property can
take on all of these values:
auto | baseline | before-edge | text-before-edge | middle | central | after-edge |
text-after-edge | ideographic | alphabetic | hanging | mathematical | inherit
which are documented here:
http://www.w3.org/TR/xsl/#alignment-baseline
I can see how "middle" might map to "middle", but what about "top" and "bottom"? Have
you tried any of these other property values?
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Frank Arensmeier" <[email protected]>
To: "Docbook Apps Help list" <[email protected]>
Sent: Monday, February 13, 2012 4:51 AM
Subject: [docbook-apps] valign on inlinemediaobject no effect?
Hi there.
I am trying to align some inline graphics nicely with the surrounding text. But,
setting the attribute valign on the imagedata element has no effect. The image stays
aligned relative to the text top whatsoever. By looking at the fo output from the
transformation process, I can see that the attribute valign is reflected to the fo
attribute "display-align" on the "external-graphic" element. If I change that to
"alignment-baseline" and set the value to "middle", everything shows up fine. Am I
missing something? Shouldn't the stylesheet distinguish between valign on
inlinemediaobjects and mediaobjects and "translate" that attribute to
"alignment-baseline" on inlinemediaobjects and "display-align" on mediaobjects?
Regards,
/frank
---------------------------------------------------------------------
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]