Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1217 Webhelp: add olink support

output: webhelp
closed-fixed
XSL (1066)
5
2014-01-20
2012-01-04
Sorin Ristache
No

The Webhelp transformation from Docbook XSL 1.76.1 does not support olink links. Please add olink support to the Webhelp transformation as in the XHTML and PDF transformations.

Discussion

  • Ordinant
    Ordinant
    2012-02-08

    My company cannot move to WebHelp format without olink support. We have a large set of DB 4 files organized into 12 books, all heavily cross-referenced with a common olink database.

     
  • David Cramer
    David Cramer
    2012-02-13

    Sorin and Ordinant,
    So olink can be implemented in different ways. Can you describe what you need? At a minimum, I can imagine that you would want a target added to the ant script that will generate the piece of the olink database for each doc. Note that it would still be up to you to create the file that wraps all the olink database fragments and that generates all the fragments before generating each document. Does that seem right?

     
  • Sorin Ristache
    Sorin Ristache
    2012-02-27

    Hi David,

    In the build.xml script of this transfomation I can see that it is based on (imports) the DocBook XHTML stylesheet so it already offers the parameters collect.xref.targets, target.database.document and targets.filename. The problem is that the olink links are not resolved. That is, if I provide values for these olink parameters I would like to have the olin links resolved in the XHTML files from the EPUB output.

     
  • Sorin Ristache
    Sorin Ristache
    2012-02-27

    Hi David,

    In the build.xml script of this transfomation I can see that it is based on (imports) the DocBook XHTML stylesheet so it already offers the parameters collect.xref.targets, target.database.document and targets.filename. The problem is that the olink links are not resolved. That is, if I provide values for these olink parameters I would like to have the olin links resolved in the XHTML files from the EPUB output.

     
  • Sorin Ristache
    Sorin Ristache
    2012-02-27

    Sorry, I mean the Webhelp output. For example I want to cross-reference between two different DocBook documents (for example two books) that will be transformed to Webhelp output.

     
  • Robert Stayton
    Robert Stayton
    2012-11-03

    • assigned_to: nobody --> bobstayton
    • status: open --> pending-fixed
     
  • Robert Stayton
    Robert Stayton
    2012-11-03

    Since webhelp is based on the xhtml stylesheet, it had the same problem as that stylesheet regarding olinking. The problem was that the target.db olink data files that need to be generated for each document would contain a DOCTYPE declaration. That prevented a target database from using a system entity reference to pull in the target.db files. The DOCTYPE was always there when using Saxon because the xsl:output element in xhtml/docbook.xsl specified the output doctype, and those could not be reset to blank in Saxon.

    The solution was to create a new xhtml/docbook-no-doctype.xsl file in the distribution, and have xhtml/chunk.xsl import that file instead of docbook.xsl. That solved the problem of DOCTYPE, and allows the stylesheet being processed by the webhelp ant file to properly resolve olinks.

    Care must be taken when setting up the target.database.document file so that it uses sitemap and the sitemap includes the "contents" directory for each document. Also, you will need to customize the ant properties so each document generates its own target.db file, either as a different filename or a different directory. But I got olinks to work in the latest snapshot build of webhelp.

     
  • Robert Stayton
    Robert Stayton
    2014-01-20

    • Status: pending-fixed --> closed-fixed