Re: [docbook-apps] whether to create separate master olink database files for for HTML and FO output

Are you using the olink database for a single 
modular document, or are you using it to link between multiple documents?  
If the latter, then all the documents in the olink database would need to get 
updated to switch from one output type to the other.  The xreftext element 
may contain output markup, which would not be compatible between html and fo 
outputs.

 

Bob Stayton
Sagehill Enterprises
DocBook Consulting


 

 

  
----- Original Message ----- 

  
From: 
  Jeff 
  Powanda 

  
To:  
  

  
Sent: Monday, March 26, 2007 5:39 
PM

  
Subject: [docbook-apps] whether to create 
  separate master olink database files for for HTML and FO output

  

  

  
In this section of Bob Stayton’s 
  book, it says that you need to create separate master olink database files for 
  HTML and FO output:

  
http://www.sagehill.net/docbookxsl/OlinkPrintOutput.html#PdfLinkingSetup

  
 

  
Is it absolutely necessary to set 
  up separate olink database files for HTML and FO output? Has anyone been able 
  to avoid using separate olink database files by specifying the olink.base.uri 
  when you generate the target.db file?

  
 

  
Regards,

  
Jeff Powanda