From: Jean Charles Delepine <delepine@u-picardie.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: make htmldocs
Date: Wed, 15 Oct 2003 13:01:22 +0200 [thread overview]
Message-ID: <20031015110122.GD994@u-picardie.fr> (raw)
In-Reply-To: <20031013185539.B1832@beton.cybernet.src>
Karel Kulhavý <clock@twibright.com> écrivait (wrote) :
> 3) Bugreport: there should be written
> "Linux kernel depends on DocBook stylesheets. You may download DocBook
> stylesheets here-and-there." in README
In README you should have read :
Please read the Changes file, as it
contains information about the problems, which may result by upgrading
your kernel.
- The Documentation/DocBook/ subdirectory contains several guides for
kernel developers and users. These guides can be rendered in a
number of formats: PostScript (.ps), PDF, and HTML, among others.
After installation, "make psdocs", "make pdfdocs", or "make htmldocs"
will render the documentation in the requested format.
And in Documentation/Changes :
Linux documentation for functions is transitioning to inline
documentation via specially-formatted comments near their
definitions in the source. These comments can be combined with the
SGML templates in the Documentation/DocBook directory to make DocBook
files, which can then be converted by DocBook stylesheets to PostScript,
HTML, PDF files, and several other formats. In order to convert from
DocBook format to a format of your choice, you'll need to install Jade
as well as the desired DocBook stylesheets.
And :
Jade
----
o <ftp://ftp.jclark.com/pub/jade/jade-1.2.1.tar.gz>
DocBook Stylesheets
-------------------
o <http://nwalsh.com/docbook/dsssl/>
Please RTFM before trying to compile your own kernel or use your
favorite distribution's binary kernel.
Sincerly,
Jean Charles
prev parent reply other threads:[~2003-10-15 11:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 16:55 make htmldocs Karel Kulhavý
2003-10-14 9:46 ` Erik Mouw
2003-10-14 10:09 ` Karel Kulhavý
2003-10-14 10:48 ` Clemens Schwaighofer
2003-10-14 11:04 ` Erik Mouw
2003-10-14 12:57 ` Karel Kulhavý
2003-10-14 11:16 ` Michael Still
2003-10-14 13:44 ` Karel Kulhavý
[not found] ` <200310140842.57178.shawnfu@willden.org>
2003-10-14 15:06 ` make htmldocs -- docbook-utils Karel Kulhavý
2003-10-14 19:50 ` make htmldocs Michael Still
2003-10-14 14:09 ` Karel Kulhavý
2003-10-15 19:37 ` Thomas Horsten
2003-10-16 19:26 ` Pavel Machek
2003-10-14 14:41 ` Karel Kulhavý
2003-10-14 19:55 ` Michael Still
2003-10-14 21:53 ` Michael Still
2003-10-14 12:51 ` Pavel Machek
2003-10-14 17:29 ` Guy
2003-10-14 17:52 ` Sam Ravnborg
2003-10-15 19:30 ` Thomas Horsten
2003-10-15 11:01 ` Jean Charles Delepine [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031015110122.GD994@u-picardie.fr \
--to=delepine@u-picardie.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox