Menu

#364 Add olink support for HTML Help output

output: HTML
closed-fixed
XSL (399)
5
2014-08-17
2006-09-19
Jan Becvar
No

Would it be possible to add olink support for HTML Help
output of XSL stylesheets. While searching the mailing
lists, I could see that this feature was planned
already for some time, but probably never realized.

Discussion

  • Robert Stayton

    Robert Stayton - 2006-10-09

    Logged In: YES
    user_id=193218

    There are two uses for olinks:
    1. Use them between modular files within the same
    document.
    2. Use them between different documents.

    In the case of the htmlhelp stylesheet, the first usage
    works, where olinks can be used to form internal links
    within an CHM file.

    Regarding linking between documents, I don't know how to
    link from one CHM file to another. Is there some standard
    syntax that is used for that? Is there a reference
    document that describes it in detail?

     
  • Robert Stayton

    Robert Stayton - 2009-03-05

    I just checked in support to htmlhelp-common.xsl to generate the olink target data file when the collect.xref.targets parameter is not set to 'no'. This generates the target data that should work for olinks in CHM files.

    However, the target.database.document (typically named olinkdb.xml) must have some specific syntax for olinks to work. Specifically, the baseuri attribute of a <document> element must look like this:

    baseuri="ms-its:mybook1.chm::/output/"

    where "ms-its:" is a required string
    "mydbook1.chm" is the name of the compiled CHM file for that document
    "::/" is a required string
    "output/" is any $base.dir parameter value used when building the HTML files.

    This set up works when the CHM files are installed into the same directory.

     
  • Robert Stayton

    Robert Stayton - 2009-03-05
    • assigned_to: nobody --> bobstayton
    • status: open --> pending-fixed
     
  • SourceForge Robot

    • status: pending-fixed --> closed-fixed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).