|
Bugzilla – Full Text Bug Listing |
| Summary: | [susehelp] HTML output without branding (.css is missing) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Karl Eichwalder <ke> |
| Component: | Documentation | Assignee: | Karl Eichwalder <ke> |
| Status: | RESOLVED FIXED | QA Contact: | Karl Eichwalder <ke> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | taroth, thomas.schraitle, wstephenson |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Documentation | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Karl Eichwalder
2005-11-23 09:29:40 UTC
I noticed this too now that I have taken over susehelp from Cornelius. Apparently different susehelp.css are also found in various packages (resmgr, susedtd, etc) throughout the distro. Could we put them in a single place instead? I really don't know, if there are any technical reasons for keeping the stylesheets seperately. Karl, do you? Adding susehelp.css to the helpsystem is okay; but we should always add a copy to the book packages. Then all tar or rpm archives stay self-contained. I'm still wondering whether the bug on 10.0 is serious enough that we should offer an update or a work around (a dummy package that would install susehelp.css into the html directories; for example, I could add it to novdoc-schema and make novdoc-schema a recommended update...). Will, feel free to comment and to re-assign the bug to me if you think I could or should do something for 10.0. Karl, I don't think any action is needed here now - we have susehelp.css in all the manuals I looked at. yes, we now ship it with all the books. |