targetdoc attribute of olink

On Sep 8, 2006, at 11:48 AM, Bob Stayton wrote:

> Yes, I think it should be optional for case of using
olinks between  
> modules in a single book.  I have filed an RFE to get
that changed.

I agree.  We use OLinks for all of our cross-references
(within a  
book and to other books).


-Steve

------------------------------------------------------------
---------
To unsubscribe, e-mail: docbook-unsubscribelists.oasis-open.org
For additional commands, e-mail: docbook-helplists.oasis-open.org

I know this is naive coming from someone just starting to
use olinks.
Please forgive me :-]

I was wondering if there could be a way to create a
target.db that
contained information for all rendered output forms instead
of
whatever the last output form was?

Perhaps this could be done via multiple trees in the
target.db keyed
to major output type (fo, html, xhtml, etc) and the profile
paramters
list?

If one document references another, it could point to the
target.db of
the other document + a fragment identifier and the default
(but
configurable) behavior of the stylesheet could create the
hard link by
choosing the mode and profile closest to that of the
document
presently being processed.

Then you could eliminate the target catalog and just use
"url/to/target.db#fragment".

What do you people think? Is it possible to create a
target.db like that?

On 9/8/06, Steven Cogorno <Steven.Cogornosun.com> wrote:
>
> On Sep 8, 2006, at 11:48 AM, Bob Stayton wrote:
>
> > Yes, I think it should be optional for case of
using olinks between
> > modules in a single book.  I have filed an RFE to
get that changed.
>
> I agree.  We use OLinks for all of our cross-references
(within a
> book and to other books).
>
>
> -Steve
>


-- 
http://chris.chiasson.nam
e/

------------------------------------------------------------
---------
To unsubscribe, e-mail: docbook-unsubscribelists.oasis-open.org
For additional commands, e-mail: docbook-helplists.oasis-open.org