[
https://issues.apache.org/jira/browse/DERBY-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742935#action_12742935
]
Rick Hillegas commented on DERBY-4349:
--------------------------------------
Thanks for the patch, Kim. I applied it to my client and can confirm that it
fixes the css links in the generated html: now they are relative filenames
pointing at stylesheets in the same directory as the generated html. I can also
confirm that this improves the spacing between some elements in the output.
Looks good.
I don't understand the issue with the copying of the stylesheets, however.
Before applying the patch, the stylesheets nevertheless were correctly copied
to the same directory as the generated html--they just weren't located by the
browser because the links pointed to garbage locations.
Thanks,
-Rick
> 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.
