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: Using HTML profiling breaks olinks and HTML navigation


I tried implementing support for conditionalized text in my documentation. I followed the instructions at http://www.sagehill.net/docbookxsl/Profiling.html and everything seemed to go smoothly. PDF output with conditionalized text works great.

 

However, I encountered a few problems with HTML output.

 

I would like chunked HTML output (several small files instead of one file), so I had been importing this stylesheet in my customization layer:

 

<xsl:import href=""../xsl/html/chunk.xsl"/>

 

To use profiling (conditions), I imported this stylesheet instead:

 

<xsl:import href=""../xsl/html/profile-chunk.xsl"/>

 

Since I’m using modular documents, I use olinks for cross-referencing. After I switched to using the profiling stylesheet, the olinks can’t be resolved. I get errors like this:

 

warning: failed to load external entity "olinkdb.xml"

Olink error: could not open target database 'olinkdb.xml'.

Error: unresolved olink: targetdoc/targetptr = 'bookid/topicid'.

 

All of the olinks resolved fine before I switched to importing the profiling stylesheet. Also, HTML navigation (for example, Previous and Next links) is now missing from the HTML output. Again, it worked fine before I imported the profiling stylesheet.

 

Has anyone encountered these problems?

 

BTW, I’m using the following tools:

  • DocBook 4.5 XSL 1.7.2
  • FOP 0.93
  • xsltproc

 

Thanks in advance for your help.

 

Regards,

Jeff Powanda

 

 



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