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

Kim Haase commented on DERBY-4349:
----------------------------------

After some thought and discussion, it probably makes the most sense to restore 
the previous behavior of copying all three files over (though only one is used 
currently), but with the docs.properties fix that makes commonltr.css at last 
accessible.

Will post a revised patch and commit it in a day or two unless I hear any 
objections.

> Documentation build files incorrectly specify missing stylesheet
> ----------------------------------------------------------------
>
>                 Key: DERBY-4349
>                 URL: https://issues.apache.org/jira/browse/DERBY-4349
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.5.2.0
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: commonltr.css, DERBY-4349.diff
>
>
> A link in the metadata for generated HTML files calls for a stylesheet that 
> is part of the DITA toolkit. There are two problems:
> 1. The stylesheet doesn't actually appear in the output directories for the 
> documentation, so it is not used.
> 2. The link currently appears with the absolute pathname of the stylesheet in 
> the temp directory for each document. For the Latest Alpha Manuals currently, 
> for example, it looks like this for a page in the Getting Started guide:
> <link href="C:\nightlies\docs-trunk\out\getstarttemp\commonltr.css" 
> type="text/css" rel="stylesheet" />
> Specifying an absolute pathname is obviously not desirable, because the 
> pathname reflects where the docs were built, not where they are installed, 
> and because the temp directory disappears after the docs are built anyway.
> There's a simple fix for each of these problems.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to