This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
[docbook-apps] bilbioid/@class="uri" and some other biblioentry rendering topics
- From: Frédéric Glorieux <frederic dot glorieux at ajlsm dot com>
- To: "docbook XSL" <docbook-apps at lists dot oasis-open dot org>
- Date: Wed, 30 Apr 2003 19:49:52 +0200
- Subject: [docbook-apps] bilbioid/@class="uri" and some other biblioentry rendering topics
Hello,
I'm using these customized templates to have a link in html
transformation for an uri biblioid. Perhaps it's of general interest?
<xsl:template match="biblioid[@class='uri']"
mode="bibliography.mode">
<<a href="{.}">
<xsl:apply-templates mode="bibliography.mode"/>
</a>>
<xsl:value-of select="$biblioentry.item.separator"/>
</xsl:template>
<xsl:template match="biblioid[@class='uri']"
mode="bibliomixed.mode">
<<a href="{.}">
<xsl:apply-templates mode="bibliomixed.mode"/>
</a>>
</xsl:template>
Other detail, docbook-xsl make an extensive use of <p/>
elements, probably to have benefits of margin-top and margin-bottom
properties. div[@class='biblioentry']/p is easy to match in css, but is
it really semantic?
We usually use a default html.css for which a <p/> is clearly
text, so first line is indent. Bad effect on a biblioentry...
In html/biblio.xsl I read
<xsl:template match="abstract" mode="bibliography.mode">
<!-- suppressed -->
</xsl:template>
Not impossible to override, but should I understand that
abstract in a biblioentry is not very useful?
Frédéric Glorieux.
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org