[
https://issues.apache.org/jira/browse/DERBY-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742948#action_12742948
]
Kim Haase commented on DERBY-4349:
----------------------------------
You're right, Rick, of course.
If I use the default build.xml file and don't modify docs.properties, three
.css files are copied into the output directory, but they are not used because
the pathname is spurious.
If I use the default build.xml file and modify docs.properties to add
"args.csspath=", the .css files are *not* copied over, so using the correct
relative pathname has no effect. (I've been defining args.csspath for a long
time so I had forgotten what happened when I didn't.)
The reason this happens is in the DITA toolkit file ditatargets.xml, but I
can't make head nor tail of it. (There's a copy-css target.)
If I modify build.xml to copy all the css files --
includes="index.html, *.css"/>
and modify docs.properties to add "args.csspath=", all three .css files are
again copied over, although since only commonltr.css is referred to, I probably
only need to copy that one. Copying all three would restore the default
behavior, though. What do you think?
> 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.
