public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mike O'Connell <mike@flame.co.za>
To: docbook-tools-discuss@sources.redhat.com
Subject: XRef link bug
Date: Tue, 27 Nov 2007 08:48:00 -0000	[thread overview]
Message-ID: <1196153302.2597.7.camel@jasmine> (raw)

Hi All

Not sure if this is still active but here goes:

While using docbook2pdf and xref links within the document I noticed
that the subsequent link created in the PDF contained a stray '>' 

"the Section called Licence Configuration>"

After some investigation I found that if I omitted the '>' in the
following line 

"<xref linkend=Licence_Configuration/>" 

so that it read 

"<xref linkend=Licence_Configuration/"

then the link would appear as it should, this, in turn, however made the
sgml invalid. Closing the xref tag using </xref> also broke the
converter. 

Is this a bug or merely a feature?

My docbook versions on Fedora Core 5:

docbook-utils-0.6.14-5
docbook-style-dsssl-1.79-4
docbook-slides-3.3.1-2.1
docbook-style-xsl-1.69.1-5
docbook2X-0.8.7-1.fc5
docbook-dtds-1.0-30
docbook-utils-pdf-0.6.14-5
docbook-simple-1.0-2.1

Kind Regards,

Mike


                 reply	other threads:[~2007-11-27  8:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1196153302.2597.7.camel@jasmine \
    --to=mike@flame.co.za \
    --cc=docbook-tools-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).