Done, and it does compile, but... in the generad HTML document, the link text is missing. For instance the test specified between the two <olink ...>my text</olink> tags does not generate a link named "my text". It just generate normal text (blah blah my text blah blah).
Is the modspec element correct i defined correct? The external document I want to refer is a glossary, and the localinfo property actually points to a glossterm element. Could that be a problem? Giuseppe. On Sat, 2001-11-24 at 03:01, Bob Stayton wrote: > > From: Giuseppe Greco <[EMAIL PROTECTED]> > > > > I'm still traying to link two different docbook > > documents... > > > > So, I did what Norm said to me last time. I introduced > > some olinks in my document. > > > > 1. I modified the document as requred: > > > > <!DOCTYPE book PUBLIC "-//QUXO//DTD DocBook V1.0//EN" [ > > <!ENTITY % English "INCLUDE"> > > <!ENTITY % projdata SYSTEM "TECHDOC//ENTITIES Project Data V1.0//EN"> > > <!ENTITY glossary SYSTEM "TECHDOC//DOCUMENT Glossary V1.0//EN" CDATA > > SGML> > > %projdata; > > ]> > > > > <book id="..."> > > ... > > <bookinfo> > > ... > > <modespec id="glossary.ms"> > > ../glossary/&proj.code;-glossary.html > > </modespec> > > </bookinfo> > > > > <chapter ...> > > <para> > > blah, blah, <olink targetdocent="glossary" linkmode="glossary.ms" > > localinfo="broadsphere">BroadSphere</olink> blah, blah ... > > </para> > > </chapter> > > </book> > > > > 2. I downloaded the olink.dsl (strange, in my distribution this file > > was missing). > > > > Now, if I have well understood, before using olinks in my document, > > a .olink file should be generated. Ok, but how (I use OpenJade)? > > > > Using olinks, file extensions must be either .sgml or .xml. isn't it? > > The .olink file is a summary of all the xref targets. > It is generated by processing the target document with > the olink.dsl stylesheet and saving the file to > the same filename as your document but with a .olink > extension. So if your document is "mybook.sgml" then > you do something like: > > jade -d olink.dsl -o mybook.olink mybook.sgml > > When the docbook.dsl stylesheet processes another > document that includes an olink with attribute > targetdocent="mybook" (as an entity reference that > points to mybook.sgml), it reads mybook.olink > to get the summary data to form the link. > > Anyone trying to use the existing olink mechanim pretty > much needs to keep a copy of Norm's document handy: > > http://docbook.sourceforge.net/projects/dsssl/doc/olinksemantics.html > > > bobs > Bob Stayton 400 Encinal Street > Publications Architect Santa Cruz, CA 95060 > Technical Publications voice: (831) 427-7796 > Caldera International, Inc. fax: (831) 429-1887 > email: [EMAIL PROTECTED]
