public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Hans-J?rgen Koch <hjk@linutronix.de>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Documentation files in html format?
Date: Fri, 10 Aug 2007 02:15:01 +0200	[thread overview]
Message-ID: <46BBAE05.3080103@gmail.com> (raw)
In-Reply-To: <20070809222735.GB23596@electric-eye.fr.zoreil.com>

On 08/10/2007 12:27 AM, Francois Romieu wrote:

> Andi Kleen <andi@firstfloor.org> :
> [...]

>> I don't think that is used by Linuxdoc. Try a make pdfdocs and see for
>> yourself.
> 
> It reminds me of an old PII but it does not really make clear how html to
> pdf conversion would improve the situation.

With HTML the source format is itself the preferred object format for many 
purposes (something which I assume you wouldn't want to claim of DocBook 
source) meaning that for those uses there is no conversion.

Which given the number of times "make *docs" has bombed out on me through 
the years I find a definite improvement. Add in that it's much easier to 
produce HTML, that it covers most all formatting needs something like the 
kernel documentation directory needs, integrates unchanged, directly and 
nicely into the effort Rob Landley is doing with collecting documentation 
online and is a format you can read with a program most users have open and 
available 100% of the time rather than requiring a complete stack of 
semi-obscure external software -- and I just don't see why anyone would want 
to argue that DocBook and its associated crapola should _not_ be buried in 
that same dark, desolate place where other abortive attempts at improvement 
such as GNU info already reside.

Rene.


  reply	other threads:[~2007-08-10  0:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 10:31 Documentation files in html format? Stephen Hemminger
2007-08-09 10:49 ` Jan Engelhardt
2007-08-09 13:08 ` Hans-Jürgen Koch
2007-08-09 13:22   ` Stephen Hemminger
2007-08-09 15:26   ` Andi Kleen
2007-08-09 14:37     ` Rene Herman
2007-08-09 15:15     ` Jarek Poplawski
2007-08-09 19:10     ` Francois Romieu
2007-08-09 19:30       ` Andi Kleen
2007-08-09 22:27         ` Francois Romieu
2007-08-10  0:15           ` Rene Herman [this message]
2007-08-10  7:40     ` Sam Ravnborg
2007-08-10 13:52       ` Stefan Richter
2007-08-10 20:12         ` Sam Ravnborg
2007-08-10 23:27           ` Rene Herman
2007-08-11  6:31             ` Stefan Richter
2007-08-11 19:12               ` Rene Herman
2007-08-11 15:53           ` Jan Engelhardt
2007-08-11 22:55           ` Randy Dunlap
2007-08-12  3:11           ` Randy Dunlap
2007-08-12  3:27             ` Sam Ravnborg
2007-09-01 18:39       ` Oleg Verych
2007-08-09 17:56 ` Bob Copeland
2007-08-09 19:14 ` Stefan Richter
2007-08-09 19:58   ` Brennan Ashton
2007-08-09 20:03 ` Jesper Juhl
2007-08-09 20:08   ` Jan Engelhardt
2007-08-10 20:17 ` Willy Tarreau
2007-08-10 20:40   ` J. Bruce Fields
2007-08-10 20:51     ` Willy Tarreau
2007-08-10 23:08       ` Sam Ravnborg
2007-08-11  5:33         ` Willy Tarreau
2007-08-11 14:19       ` J. Bruce Fields
2007-08-11 14:17         ` Willy Tarreau
2007-08-11 23:00           ` Randy Dunlap
2007-08-12  3:12           ` Randy Dunlap
2007-08-12 13:10             ` Stefan Richter
2007-08-12 15:43               ` Sam Ravnborg
2007-08-12 18:25                 ` Stefan Richter
2007-08-11 23:12   ` Randy Dunlap
2007-08-12  3:12   ` Randy Dunlap
     [not found] <8QdB3-87O-7@gated-at.bofh.it>
     [not found] ` <8QdUr-5j-11@gated-at.bofh.it>
2007-08-09 12:34   ` Bodo Eggert
2007-08-09 12:41     ` Jan Engelhardt
2007-08-09 13:29       ` Bodo Eggert

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=46BBAE05.3080103@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=hjk@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=shemminger@linux-foundation.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