OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] Olinking and Chunked HTML Transformations

Hi Ray,
Extracting the target information can be done at the same time as the transformation for the current document. If you set the collect.xref.targets to 'yes', then the process first collects the data and write it into target.db, and then processes the content and olinks by reading back the data from the file.  If you use olinks, you still need to set up a minimal olinkdb.xml file that associates the targetdoc="foo" with the target.db data, as described in the book. 
targets.filename="target.db"  (this is the default value)
Contents of olinkdb.xml:
<?xml version="1.0"?>
<!DOCTYPE targetset [
<!ENTITY data SYSTEM "target.db">
  <document targetdoc="foo">
Bob Stayton
Sagehill Enterprises
DocBook Consulting
----- Original Message -----
From: Ray Miller
Sent: Wednesday, April 26, 2006 3:17 PM
Subject: [docbook-apps] Olinking and Chunked HTML Transformations

docbook-rng-5.0b5 docbook-xsl-snapshot (current) oxygenxml-7.1.0 ( eclipse-3.1.2 plugin )


A little confused implementing internal olinks within chunked html transformations.


Consider the following olink element:


<olink targetdoc="foo" targetptr="bar"/>


Targetdoc is a required property. How is targetdoc applied in the context of a chunked html transformation where the olink resolves to a target within the same transformation? Extracting targetdoc info from preprocessed target.db output can be a maintenance nightmare in a rapidly evolving docbook project.


Have Bob Staytonís excellent book (purchased a copy) but upon reviewing olink sections, remain unsuccessful in olink resolution within chunked html transformations.


Examples, including usage of stringparms target.database.document, targets.filename and use.local.olink.style, would be greatly appreciated.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]