Hi Bob,
Thanks for the help.
On Wed, 28 Oct 2015 12:06:47 -0700
Bob Stayton <b...@sagehill.net> wrote:
> I presume you mean for an author element in a para, as opposed to an
> author in an info element. The latter is processed by a template in
> fo/titlepage.xsl starting like this:
>
> <xsl:template match="author" mode="titlepage.mode">
>
> and it does output orgname and email.
Yes, I do mean in a <para>, or even a <term> in a varaiablelist.
(Although, come to think of it, in HTML output for a book
when the copyright section is put in a separate page
the copyright link comes out too close (vertically) to
the author in the <info>. This might possibly be due
to something I did in my CSS style though.)
> An inline author element is processed by a template in fo/inline.xsl
> starting like this:
>
> <xsl:template match="author">
>
> which just calls a template named 'person.name'. You would need to
> customize that template to be more like the one in titlepage.xsl.
>
> Or you could try something like this:
>
> <xsl:template match="author">
> <xsl:apply-templates select="." mode="titlepage.mode"/>
> </xsl:template>
>
> and then they would have the same behavior.
The latter looks like it might be spiffy.
I do have a question about the above approaches. Customizing
a 'person.name' template, or applying templates with
mode="titlepage.mode" sounds dangerously like invoking
an undocumented API. Is there any sort of guarantee anywhere
that this sort of thing will continue to work over time?
I would think that the stylesheet authors should be free
to alter the internal implementation as desired.
I don't have serious concerns here, but do like to know
when I'm bending the rules.
Thanks again for the help.
Regards,
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
