This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


Well, don't forget that you asked...

The olink data is generated by applying templates to an element in 'xref-fo'
mode. There is one such template for a lot of elements that contain a title
child, including formalpara.  It processes the element in
'object.xref.markup' mode. That mode uses the gentext templates from the
'xref' context in common/en.xml.  Then it uses the substitute.markup
template to fill in the '%t' title placeholder.  It uses mode=title.markup,
with the template parameter 'allow-anchors' set to zero.  When allow-anchors
is set to zero, then it is processed in no.anchor.mode. In no.anchor.mode,
any link, ulink, olink, and xref is not fully processed, only its child text
is used (which doesn't work for an empty olink or xref, of course).

For variablelist, there is a separate template in 'xref-to' mode that is
more simple. It just applies templates to the first <term> child of the
varlistentry.  Since there is no title involved, there is not a no-anchor
mode available.  So all links are fully processed, leading to the message
you saw.  That is probably a bug, though, as this could lead to HTML <a>
anchors being nested.


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:58 PM
Subject: [docbook-apps] Re: Olinks not processed


> > * Bob Stayton <obof@fntruvyy.arg> [2004-06-08 15:07:47 -0700]:
> >
> > 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>">
>
> why doesn't
>
> <formalpara id="def-file-enc"><title>symbol-macro &def-file-enc;</title>
>
> trigger the same error?
> what's so special about varlistentry?
>
> -- 
> 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>
> If you think big enough, you'll never have to do it.
>
>
> 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/.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]