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] Updated: (DERBY-4349) Documentation build files incorrectly specify missing stylesheet
Date Thu, 20 Aug 2009 16:56:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase updated DERBY-4349:
-----------------------------

    Attachment: DERBY-4349-2.diff

Attaching patch that copies over all three .css files, just in case. Reproduces previous behavior
except that the file pointed to by the link will now be accessible.

> 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-2.diff, 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.


Mime
View raw message