docbook-apps

  • 1.  xref into a biblioset?

    Posted 02-10-2014 01:23
    Hi,

    How can I make my xref select a specific biblioset within a biblioentry?

    I looked about on ways to customise the xrefstyle, but it doesn't seem any of the default ones<http://www.sagehill.net/docbookxsl/CustomXrefs.html> are applicable. I suspect the core issue anyway is that the xml:id is set on the biblioentry and none of the biblioset's have them.
    --

    Vadim Peretokin
    Clinical Information Modeller
    nehta - National E-Health Transition Authority
    Level 2, 10 Browning St, West End, QLD 4101, Australia
    Phone: (0) 3023 8573
    Email: vadim.peretokin@nehta.gov.au<mailto:firstname.lastname@nehta.gov.au>
    Web: www.nehta.gov.au<http://www.nehta.gov.au>


    The information contained in this e-mail message and any accompanying files is or may be privileged or confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail and any attachments may be subject to copyright. Copyright material should not be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. NEHTA does not make any representations or give any guarantees in respect of the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore NEHTA does not accept any liability for the contents of this message or attached files.



  • 2.  Re: [docbook-apps] xref into a biblioset?

    Posted 02-10-2014 17:49
    Hi Vadim,
    I'm afraid it won't be easy to link to a specific biblioset if it does
    not have an xml:id. Are those entries not editable? If you can xref to
    the xml:id on biblioset, it will generate the biblioset/title by default.

    However, I notice that in FO output, the xml:id is not copied through
    the the output (it is in HTML output). So the title will be generated,
    but the link will be dead in the output. That's a deficiency that
    requires this workaround:

    <xsl:template match="d:biblioset" mode="bibliography.mode">
    <fo:inline>
    <xsl:attribute name="id">
    <xsl:call-template name="object.id"/>
    </xsl:attribute>
    <xsl:apply-templates mode="bibliography.mode"/>
    </fo:inline>
    </xsl:template>



    Bob Stayton
    Sagehill Enterprises
    bobs@sagehill.net

    On 2/9/2014 5:23 PM, Vadim Peretokin wrote:
    > Hi,
    >
    > How can I make my xref select a specific biblioset within a biblioentry?
    >
    > I looked about on ways to customise the xrefstyle, but it doesn't seem any of the default ones<http://www.sagehill.net/docbookxsl/CustomXrefs.html> are applicable. I suspect the core issue anyway is that the xml:id is set on the biblioentry and none of the biblioset's have them.
    > --
    >
    > Vadim Peretokin
    > Clinical Information Modeller
    > nehta - National E-Health Transition Authority
    > Level 2, 10 Browning St, West End, QLD 4101, Australia
    > Phone: (0) 3023 8573
    > Email: vadim.peretokin@nehta.gov.au<mailto:firstname.lastname@nehta.gov.au>
    > Web: www.nehta.gov.au<http://www.nehta.gov.au>
    >
    >
    > The information contained in this e-mail message and any accompanying files is or may be privileged or confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail and any attachments may be subject to copyright. Copyright material should not be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. NEHTA does not make any representations or give any guarantees in respect of the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore NEHTA does not accept any liability for the contents of this message or attached files.
    >