[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: DOCBOOK-APPS: Bug in the xhtml/chunk xsl-stylesheet title anchor
On Mon, Mar 17, 2003 at 12:50:59PM -0500, Gary Lawrence Murphy wrote: > > I'm still hunting through to see if there was something I'd done > wrong, but on using the docbook-xsl-1.60.1 through xsltproc I get > a title page with the markup as follows: > > <div> > <h1 class="title"> > <a id="UserGuide"/>Sportwire II: SportPage User Guide ^ ----------------------^ > </h1> > </div> > > ie, it is missing the closing </a> after the title string Name anchors (in this case id anchors) in DocBook output are empty elements, and this XHTML output is using the XML syntax for empty element. In HTML output, this would just be <a name="UserGuide"></a>. Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 The SCO Group fax: (831) 429-1887 email: bobs@sco.com Received: (qmail 24131 invoked by uid 60881); 20 Mar 2003 18:31:41 -0000 Received: from bobs@sco.com by hermes by uid 0 with qmail-scanner-1.15 (spamassassin: 2.43. Clear:SA:0(-4.3/8.0):. Processed in 0.315849 secs); 20 Mar 2003 18:31:41 -0000 X-Spam-Status: No, hits=-4.3 required=8.0 Received: from unknown (HELO scobob.pdev.ca.caldera.com) (132.147.65.90) by mail.oasis-open.org with SMTP; 20 Mar 2003 18:31:41 -0000 Received: by scobob.pdev.ca.caldera.com (Postfix, from userid 1528) id 08E5B5452B; Thu, 20 Mar 2003 11:24:38 -0800 (PST) Date: Thu, 20 Mar 2003 11:24:38 -0800 From: Bob Stayton <bobs@sco.com> To: Scott Shepard <scottdavidshepard@hotmail.com> Cc: docbook-apps@lists.oasis-open.org Subject: Re: DOCBOOK-APPS: database reference database Message-ID: <20030320112438.D20682@sco.com> References: <F19vg58w1Dxvq7t2JIs00001a11@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <F19vg58w1Dxvq7t2JIs00001a11@hotmail.com>; from scottdavidshepard@hotmail.com on Mon, Mar 17, 2003 at 03:00:08PM -0500 On Mon, Mar 17, 2003 at 03:00:08PM -0500, Scott Shepard wrote: [stuff deleted] > Also, I might use definitions from other sources, that I would want to make > explicit, so I would like to use the "database" feature. glossdef does not > seem to allow <xref>, according to DocBook TDG v2.0.8. Not true. glossdef requires some block element like <para>, and <para> permits <xref> > Assuming I have the correct style, there seems to be no way to have the > glossary database and allow it to reference the biblio database. Unless I > create some sort of glossary/biblio file and include it into the main > DocBook instance. But then I do not have the convenience of having the words > I use automatically selected from the database and inserted into the HTML. I looked at the XSL a little closer, and the restriction is even stronger than that. If you are using a glossary collection, any cross references in it must be to targets within the glossary collection only. You cannot reference to targets back in the main document. If you could, then I think references to the biblioentries would work, because they have their id appearing in the main document (so that they can be pulled from the bibliography collection). The stylesheet uses the XSL document() function to open the glossary collection file. I think what happens is that the processor changes the processing context to that document. Only IDs within that context are recognized. What is even more dangerous, however, is that xrefs within the glossary collection will be recognized, even if the target glossentry is not pulled into the main document. Let's say you include glosstermA in your document, so the processor pulls that glossentry from the glossary collection into your document's glossary and formats it. If the glossdef for glosstermA has an xref to glosstermB that you don't include in your document, then it will form a link (and not report an error) to glosstermB, but glosstermB won't actually appear in your document's glossary. It forms a link that doesn't work when the user clicks on it. So even cross referencing within your glossary collection (as with See and See also) can lead to problems if you don't reference all the glossentries that are needed. Cross referencing within a glossary collection should probably be avoided for that reason. -- Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 The SCO Group fax: (831) 429-1887 email: bobs@sco.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]