db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-3006) Documentation: Need ability to link from one manual to another
Date Wed, 10 Sep 2014 19:55:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129002#comment-14129002

Kim Haase commented on DERBY-3006:

Still desirable, though not achievable with current tools.

> Documentation: Need ability to link from one manual to another
> --------------------------------------------------------------
>                 Key: DERBY-3006
>                 URL: https://issues.apache.org/jira/browse/DERBY-3006
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Kim Haase
> It would be desirable to be able to create usable links from a topic in one manual to
a topic in another. At present, in the HTML Pages version, the linked-to topic opens in the
right-hand frame, replacing the current topic (so that the context of the topic is lost).
And in the PDF and the HTML one-page versions, the links do not work at all. Both of these
issues appear to be toolkit problems.
> According to Andrew McIntyre, it should be possible to make the linked-to HTML Pages
topic open in a new window if a new target attribute is created. Would this include making
the entire manual open in the window, with the TOC on the left and the topic on the right?
> In the HTML one-page version (and presumably the PDF), if the link in, for example, a
Getting Started manual DITA file is to "../adminguide/cadminnetservsecurity.dita#cadminnetservsecurity",
the tools truncate it to "#cadminnetservsecurity" -- a link within the current manual, not
the one linked to, and therefore a bad link. 
> In order to say we have the ability to link to other manuals, we'd need to make both
these fixes.
> DERBY-79 had this as one of four requests; the other three have been met, so we closed
that bug, and I'm refiling this request as a separate issue.

This message was sent by Atlassian JIRA

View raw message