<html>
I have encountered a very strange problem when rendering XSL FO to PDF
using RenderX XEP 3.2.2 (and some earlier versions, as well). The
situation is easy enough to describe:<br>
<br>
I am writing a large standards document using XML. In that
document, I have a rule (a list element) whose text contains a
superscript. Here's an abstract of that XML:<br>
<dl>
<dd><item>If <emph>MAX</emph> is equal to
2<super>63</super>-1 (9,223,372,036,854,775,807) and
<emph>MIN</emph> is equal to -2<super>63</super>
(-9,223,372,036,854,775,808), then <emph>REST</emph>
is:<br>
<br>
</dl>When that XML is transformed by my XSLT stylesheet into XSL FO, it
looks like this:<br>
<dl>
<dd><fo:list-block provisional-label-separation="3pt"
space-before.optimum="6pt"
provisional-distance-between-starts="18pt"><br>
<br>
<dd><fo:list-item id="'generate_id()'"
space-before.optimum="8pt" hyphenate="true">
<dd><fo:list-item-label end-indent="label-end()">
<dd><fo:block text-align="start">1)</fo:block>
<dd></fo:list-item-label>
<dd><fo:list-item-body start-indent="body-start()">
<dd><fo:block>If <fo:inline
font-style="italic">MAX</fo:inline> is equal to
2<fo:inline baseline-shift="super"
font-size="smaller">63</fo:inline>-1
<dd>(9,223,372,036,854,775,807) and <fo:inline
font-style="italic">MIN</fo:inline> is equal to
<dd>-2<fo:inline baseline-shift="super"
font-size="smaller">63</fo:inline>
(-9,223,372,036,854,775,808), then <fo:inline
font-style="italic">REST</fo:inline>
<dd>is:<br>
<br>
</dl>I have attached a larger abstract from the XSL FO to this message,
although I doubt that additional value will be gained from examining that
larger abstract. <br>
<br>
The result of rendering the XSL FO into PDF is a list element in which
the list item label (in this case, "1)") to be raised above the
baseline of the list item body's baseline...in fact, it is raised to the
baseline of the superscripts on the first line of the list item body!
<br>
<br>
This is demonstrated in the 1-page PDF file that I attached to this
message. <br>
<br>
Is there something wrong with my XSL FO, or is this a bug (possibly
already reported?) in XEP? <br>
<br>
Thanks,<br>
Jim</html>