Re: [docbook-apps] Re: Olinks not processed

["Bob Stayton" <bobs at sagehill dot net>]

What are your options?  I would create two entities, one for the text and
one for the olink that contains the first entity.  Then you can use the
text-only entity in the term, and the olink version everywhere else.  If you
change the text, you are still only changing one entity.  That also avoids
creating a link that goes to itself, which is kind of annoying or confusing.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Sam Steingold" <sds@gnu.org>
To: <docbook-apps@lists.oasis-open.org>
Sent: Tuesday, June 08, 2004 3:43 PM
Subject: [docbook-apps] Re: Olinks not processed


> > * Bob Stayton <obof@fntruvyy.arg> [2004-06-08 15:07:47 -0700]:
> >
> > I tracked down the cause of those messages.
> Thanks!
>
> > It turns out they are valid errors.
> oops...
>
> > The olinks in question are contained in varlistentry term elements.
> > For example:
> >
> > <varlistentry id="path-enc"><term>&path-enc;</term>
> >
> > where the &path-enc; entity is an olink:
> >
> > <!ENTITY path-enc "<olink targetdoc='impnotes'
> >
targetptr='path-enc'><varname>CUSTOM:*PATHNAME-ENCODING*</varname></olink>">
> >
> > The olink collection process examines every element with an id attribute
and
> > extracts the xref text that would be generated if it were xref'ed to.
In
> > the case of a varlistentry, the generated xref text is the contents of
its
> > <term> element.  So when it goes to apply stylesheet templates on the
term
> > content to generate that text, it must process the olink to get its
text.
> > That's why it is asking for the $target.database.document.
>
> so we are dealing with a recursion here, right?
> I am generating tdb-pile.xml, and for that I need tdb-pile.xml to be
> present already.
>
> > But in your case, there is another problem: the olink points to
> > itself.  It looks to me like the document being processed
> > targetdoc="impnotes", and the 'path-enc' id is on the varlistentry.
> > So the content of this term is pointing to its varlistentry parent.
> > Is that what is really intended?
>
> Yes.  I want to use the entity everywhere, including the place where it
> is first mentioned - for consistency, mostly.
>
> Now I understand when this error appeared:
> I used to use <link> in the path-enc definition and I switched to
> <olink> to be able to use path-enc in the man page too.
>
> OK, so what are my options - short of replacing
>
> <varlistentry id="path-enc"><term>&path-enc;</term>
>
> with
>
> <varlistentry><term><firstterm>&path-enc;
>    <indexterm id="path-enc" significance="preferred">
>     <primary id="path-enc-i"><varname>*PATHNAME-ENCODING*</varname>
>  </primary></indexterm></firstterm></term>
>
> (on the second thought, this isn't too bad either...)
>
> thanks a lot for your kind help!
>
> --
> Sam Steingold (http://www.podval.org/~sds) running w2k
> <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
> <http://www.mideasttruth.com/> <http://www.honestreporting.com>
> Man has 2 states: hungry/angry and sate/sleepy.  Catch him in transition.
>
>
> To unsubscribe from this list, send a post to
docbook-apps-unsubscribe@lists.oasis-open.org, or visit
http://www.oasis-open.org/mlmanage/.
>
>
>



To unsubscribe from this list, send a post to docbook-apps-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.