OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [docbook-apps] Footnote marks in FO output

> That was a thought of mine as well.  I'm struggling to think of a case
> where that would break something, but I don't know.  Any 
> inline graphic
> that is tall enough, for example, I suspect would break 
> because of this. 
> Mind you, and inline graphic causing a baseline shift will 
> look similarly
> ugly, IMHO.

This is the one problem I've considered with this approach.  But, like you
say, no matter what you do with these graphics, you're going to end up with
something ugly.  If I were to encounter an inline graphic in our
documentation that was taller than the line-height, I'd either shrink the
graphic or break it out into a separate block.

> > If that does cause problems, a template like this would 
> probably handle
> > 90% of the cases:
> >
> > <xsl:template
> > 
> match="para[.//footnote|.//footnoteref|.//superscript|.//subscript]">
> >  <fo:block line-height-shift-adjustment="disregard-shifts">
> >   <xsl:apply-imports/>
> >  </fo:block>
> > </xsl:template>
> Again, I thought of something like this (though thanks for 
> the concrete
> implementation -- I did not get that far), but will this 
> catch everything?

This probably won't catch everything.  It will probably come very close,
though, depending on where you tend to place footnotes in your
documentation.  In most documentation, I would guess that about 90% of
super- and sub-scripts (either using those tags or the <footnote/> tag) are
contained within <para/> elements.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]