Hi Karen,
If you are going to use an xml:id attribute value for the targetdoc, it
should be that of the top level element in your assembled book. In your
example, you seem to be referring to a chapter, so I don't think that's
quite right. The targetdoc value needs to cover all the content of an
assembled book, not just one chapter. Think of an olink as a two-part
address: the first part (targetdoc) references the book, and the second part
(targetptr) references a point within that book. Only when you mean to link
to the book element itself would they match.
Bob Stayton
Sagehill Enterprises
----- Original Message -----
From: "Karen Schneider" <>
To: "docbook-apps" <>
Sent: Friday, September 04, 2009 9:37 AM
Subject: [docbook-apps] Re: olink element question
> Urp, correction:
>
> See the chapter on <olink targetdoc="lists" targetpr="lists">creating
> lists</olink>
>
> Karen
>
> On Fri, Sep 4, 2009 at 12:35 PM, Karen Schneider<>
> wrote:
>> I am working on a styleguide and want to clarify naming conventions
>> for the olink element. I still am struggling to understand this
>> element so want to make sure that the following is correct (in
>> reference to a file named filenames.xml):
>>
>> For simplicity's sake, use the document's xml:id attribute as the
>> document identifier; it will then function as both the targetdoc and
>> targetptr element. So the olink reference for this file would be
>> filenames, as in this example:
>>
>> See the chapter on <olink targetdoc="lists" targetpr="lists"</olink>
>>
>> Thanks -- I don't know why I have such a block about the olink element.
>>
>> --
>> --
>> | Karen G. Schneider
>> | Community Librarian
>> | Equinox Software Inc. "The Evergreen Experts"
>> | Toll-free: 1.877.Open.ILS (1.877.673.6457) x712
>> |
>> | Web: http://www.esilibrary.com
>>
>
>
>
> --
> --
> | Karen G. Schneider
> | Community Librarian
> | Equinox Software Inc. "The Evergreen Experts"
> | Toll-free: 1.877.Open.ILS (1.877.673.6457) x712
> |
> | Web: http://www.esilibrary.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
>
