[ docbook-Bugs-3469357 ] Webhelp: add olink support

[SourceForge.net <no...@so...>]

Bugs item #3469357, was opened at 2012-01-04 02:54
Message generated for change (Comment added) made by sorin_ristache
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3469357&group_id=21935

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: XSL
Group: output: webhelp
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sorin Ristache (sorin_ristache)
Assigned to: Nobody/Anonymous (nobody)
Summary: Webhelp: add olink support 

Initial Comment:
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.

----------------------------------------------------------------------

>Comment By: Sorin Ristache (sorin_ristache)
Date: 2012-02-27 00:15

Message:
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.

----------------------------------------------------------------------

Comment By: Sorin Ristache (sorin_ristache)
Date: 2012-02-26 23:31

Message:
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.

----------------------------------------------------------------------

Comment By: Sorin Ristache (sorin_ristache)
Date: 2012-02-26 23:31

Message:
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.

----------------------------------------------------------------------

Comment By: David Cramer (dcramer)
Date: 2012-02-13 13:54

Message:
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? 

----------------------------------------------------------------------

Comment By: Ordinant (ordinant)
Date: 2012-02-08 12:37

Message:
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. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3469357&group_id=21935