2003-12-01
| Revision History | ||
|---|---|---|
| Revision 1.0 | 2003-12-01 | xx |
| first official release | ||
| Revision 0.9 | 2003-11-01 | xx |
| first draft | ||
Abstract
This is a sample DocBook XML HOWTO which has been constructed to serve as a document template.
Table of Contents
Provide a good overview and anything else you may think is needed in this area. Looking at other HOWTOs may assist in providing ideas.
This document, Sample XML HOWTO, is copyrighted (c) 2002 by author_name. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is available at http://www.gnu.org/copyleft/fdl.html.
Linux is a registered trademark of Linus Torvalds.
No liability for the contents of this document can be accepted. Use the concepts, examples and information at your own risk. There may be errors and inaccuracies, that could be damaging to your system. Proceed with caution, and although this is highly unlikely, the author(s) do not take any responsibility.
All copyrights are held by their by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Naming of particular products or brands should not be seen as endorsements.
In this document, I have the pleasure of acknowledging:
Individual 1 <someone1 (at) somewhere.org>
Individual 2 <someone2 (at) somewhere.org>
Feedback is most certainly welcome for this document. Send
your additions, comments and criticisms to the following
email address : <xxx@xxx.xxx>.
Pointers to available translations are nice. Also your translators tend to give very important inputs.
French Translation
provided by Individual <someone (at) somewhere.fr>
German Translation
provided by Individual <someone (at) somewhere.de>
This area contains general troubleshooting information, if applicable. The question/answer format works best (like a FAQ).