| Online resources for finding solutions to problems | ||
|---|---|---|
 | Chapter 1. Introduction |  |
| Online resources for finding solutions to problems | ||
|---|---|---|
| | Chapter 1. Introduction | |
If you run into problems with the DocBook XSL stylesheets that aren't addressed anywhere in this guide, you can use a number of online resources to find solutions.
First try searching the archives of the docbook-apps
mailing list for keywords related to the problem. There is a good chance that someone else has run into something similar. Archives of
the list are available at two different sites: an archive at OASIS (which also hosts the actual mailing
list) and an archive at
Red Hat.
If, for example, you are seeing a specific error message, trying cutting and pasting the error message (or some part of it) into the search form for the mailing list archives.
You can get help in real time on the #docbook channel on
irc.openprojects.net. If your browser
supports IRC URLs (or, like Mozilla, has a built-in IRC
client), you can access the channel by entering the
following URL in your browser:
If you can't find a solution in the docbook-apps or on the
#docbook, you
should try posting a question to docbook-apps. To subscribe
to the list, send a “subscribe” message to:
To post a message to the list, send it to:
Please read the list guidelines first, and to include examples of your DocBook source document and your output (for example, HTML or FO output) along with details about the tools you're using (including version numbers of the tools).
Don't include attachments when you post to docbook-apps—the
mailing list management software automatically strips out
attachments. If you have an long example or an output
format that you can't paste into your message, post it to
a Web site, and then include the URL in your message
to the list.
The DocBook Wiki website collects contributions from DocBook users and makes them available to the world.
If you find something that seems to be a legitimate bug in the DocBook XSL stylesheets, you can file a bug report at the DocBook Open Repository site at SourceForge. If instead you want to request an enhancement to the stylesheets, file a feature request at the SourceForge site.
You will need to have a SourceForge user account to file a bug report or feature request. This requirement makes it easier follow up on bug reports. If the DocBook XSL stylesheet developers need to get more details about a specific bug report, it's difficult to follow up on it if it was submitted anonymously.
You can register for an account at the SourceForge site.
| DocBook XSL: The Complete Guide - 3rd Edition | PDF version available | Copyright © 2002-2005 Sagehill Enterprises |
| |  | |
| Chapter 1. Introduction |  | Chapter 2. XSL processors |