Re: [docbook-apps] can anyone recommend a more/better "marked up" form of...

["Chris Chiasson" <chris@chiasson.name>]

Using this recommendation eliminates the problems I had in the following thread:

http://www.oasis-open.org/archives/docbook-apps/200609/msg00091.html

P.S. AFAIK db5 presently requires olink's targetdoc attribute, so one
must also include that.

On 9/11/06, Bob Stayton <bobs@sagehill.net> wrote:
> > Does olink have any functionality similar to that of endterm for xref?
>
> I'm not clear why you need endterm with olink.  You can use an olink inside
> a citation to get the same functionality as an xref inside a citation, but
> with the advantage of no id/idref validation.  In other words:
>
> <citation><olink targetptr="JSCET"/></citation> should produce [JSCET] as a
> hot link in the output, assuming that the biblioentry id is "JSCET" and
> there is no abbrev element (which would be used as the hot text instead of
> the id).
>
> Bob Stayton
> Sagehill Enterprises
> DocBook Consulting
> bobs@sagehill.net
>
>
> ----- Original Message -----
> From: "Chris Chiasson" <chris@chiasson.name>
> To: "Ron Catterall" <ron@catterall.net>
> Cc: <docbook-apps@lists.oasis-open.org>
> Sent: Saturday, September 09, 2006 5:14 AM
> Subject: Re: [docbook-apps] can anyone recommend a more/better "marked up"
> form of...
>
>
> > Unfortunately, I compose my master document from several files that
> > are xi:included. Since the linkend attribute of biblioref and he same
> > attribute of xref uses the ref/idref scheme for validation, I am
> > unable to use biblioref and xref for citations unless I am inside my
> > Bibliography.xml document.
> >
> > Does olink have any functionality similar to that of endterm for xref?
> >
> > On 9/9/06, Ron Catterall <ron@catterall.net> wrote:
> >> the problem is that <citation> allows PCDATA.  <biblioref> has to be a
> >> link.
> >>
> >> if JSCET is a link to a <bibliography> item try:
> >> <citation><biblioref linkend="JSCET"/> (p.805)</citation>
> >> or, even better, just:
> >> <biblioref linkend="JSCET"/> (p.805)
> >>
> >> <biblioref> is unambiguous to any machine processing.  <citation> has
> >> multiple meanings - including PCDATA and many others.  With
> >> <bilioref> you can construct your <bibliography> section of
> >> <bibliomixed> automatically if this links to a master file of biblio
> >> refs.
> >> You could of course use <xref> - but that will point to just about
> >> anything.
> >>
> >> Ron
> >>
> >>
> >> see recent emails about this from Bob and Jirka, especially
> >>
> >> Hi Jirka,
> >> Yes, I think his point was that this is a bug in the stylesheet.
> >> Specifically this template in html/inline.xsl:
> >>
> >> <xsl:template match="citation">
> >>   <!-- todo: integrate with bibliography collection -->
> >>   <xsl:variable name="targets" select="(//biblioentry |
> >> //bibliomixed)[abbrev = string(current())]"/>
> >>   <xsl:choose>
> >>     <xsl:when test="$targets">
> >>       <xsl:call-template name="xref">
> >>         <xsl:with-param name="targets" select="$targets"/>
> >>       </xsl:call-template>
> >>     </xsl:when>
> >>     <xsl:otherwise>
> >>       <xsl:message>
> >>         <xsl:text>Citation to nonexistent publication abbrev:
> >> </xsl:text>
> >>         <xsl:value-of select="."/>
> >>       </xsl:message>
> >>       <xsl:text>[</xsl:text>
> >>       <xsl:call-template name="inline.charseq"/>
> >>       <xsl:text>]</xsl:text>
> >>     </xsl:otherwise>
> >>   </xsl:choose>
> >> </xsl:template>
> >>
> >> The case when there is no matching target should not generate an
> >> error message because such a match is not required.  The problem, of
> >> course, is trying to guess when a target was intended but none was
> >> found because of a typo.  Since this is PCDATA, I don't think there
> >> is any way to tell. I usually recommend people use xref directly if
> >> they want a link that can be verified.
> >> Bob Stayton
> >>
> >> Yes, indeed. But in scientific publishing it is usually more
> >> convenient to use abbrev/citation then @id/xref. Anyway I removed
> >> warning and put FO code into shape with HTML code.
> >> Jirka
> >>
> >>
> >>
> >> ><citation>JSCET</citation>, p 805
> >> >
> >> >?
> >> >Thanks.
> >> >
> >> >--
> >> >http://chris.chiasson.name/
> >> >
> >> >---------------------------------------------------------------------
> >> >To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> >> >For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
> >>
> >>
> >> --
> >> Ron Catterall, Phd, DSc                         email: ron@catterall.net
> >> Prolongacion de Hidalgo 140
> >> http://catterall.net/
> >> San Felipe del Agua                                     tel: +52 951 520
> >> 1821
> >> Oaxaca      68020       Mexico                          fax: +1 530 348
> >> 8309
> >>
> >
> >
> > --
> > http://chris.chiasson.name/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
> >
> >
> >
>
>
>


-- 
http://chris.chiasson.name/