Thanks, Hussein, for looking into this. I was able to change our style sheets to switch the order of the basic-link and inline elements. It now works.
--Andy On 11/24/2010 4:45 AM, Hussein Shafie wrote: > Andy Black wrote: >> The attached XSL-FO file contains several endnotes which are to appear >> in superscript and also be a link to the endnote text at the end of the >> document. The XSL-FO renders correctly using RenderX XEP. But the Word >> 2003 and Open Office Writer outputs of XSL Utility ignore the >> superscript in the text (the endnote text at the end is just fine). >> >> The XSL-FO has an inline element with a baseline-shift="super" attribute >> in it. The crucial distinction seems to be that this is ignored by the >> XSL Utility when the text of the inline contains a basic-link. If the >> order of the inline and basic-link are reversed, then the superscript is >> rendered correctly in Word 2003 and Open Office Writer output. >> >> Is this by design? >> > No. > > I've looked at the code and I don't see what could be done by XMLmind > XSL-FO Converter to improve the situation. > > ODT example: > > <fo:inline baseline-shift="super"><fo:basic-link > internal-destination="AAA">TTT... > > is trivially translated to: > > <text:span text:style-name="ZZZ"><text:a xlink:href="#AAA">TTT... > > which is valid OpenDocument. > > Now it seems that Open Office Writer does not ``cascade'' the > style:text-position="NNN" style from the text:span parent to the text:a > child. Other text styles (e.g. font-style, font-weight) are of course > properly ``cascaded''. > > Same situation for the .docx output. > X-Quarantine ID /var/spool/MD-Quarantine/06/qdir-2010-11-24-06.45.23-001 > -- XMLmind FO Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xfc-support
