Bug 10944
| Summary: | DSSSL Sheets producing bad sheets | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | David Mason <dcm> |
| Component: | stylesheets | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | CC: | rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-05-09 17:17:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Fixed in stylesheets-1.54.13rh-1; I decided to include the docbook DSSSL version in the package version to simplify things a little. Off to bang on psgml some more. This bug has previously been reported. Look at kdenetwork bugs. However, the querry does not work when searching for bugs now. See bugreports 4286 and 2990. Typically, your ISP will assign you a host name of "yourloginname.provider.sub". For instance I dial into inlink and my username is djl002 so: djl002.inlink.com. FIXED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *** Bug 11061 has been marked as a duplicate of this bug. *** fixed in errata going out shortly. |
There is a bug identified by Norman Walsh, the creator of the DocBook Modular Stylesheets that deals with the proper creation of TeX for the pa and pdf backends. The problem produces TeX errors similar to: "! Text line contains an invalid character. l.7280 {^^@ ^^@}\def\sbNom% A funny symbol that I can't read has just been input. Continue, and I'll forget that it ever happened." The new DSSSL sheets found at http://nwalsh.com/docbook/dsssl/db154.zip fix the problem. We should make a new rpm as soon as possible as the mailing lists are filling up with people complaining about their broken Red Hat SGML systems.