All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Using asciidoc for README.INSTALL
Date: Mon, 13 Aug 2012 01:08:56 +0200	[thread overview]
Message-ID: <50283788.8040802@grinta.net> (raw)
In-Reply-To: <502834AB.4000402@xenomai.org>

On 13/08/2012 00:56, Gilles Chanteperdrix wrote:
> Since my aim is to generate html, I am comparing the html versions of
> the user documentations of the two projects, each made with its own tool:
> http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html
> http://www.methods.co.nz/asciidoc/userguide.html
> 
> Maybe reStructuredText is good for python documentation, but apparently
> not for generating good looking html (let alone the fact that the
> document describing reStructuredText syntax is called "specification",
> not "user guide").

I'm sure you know that how HTML looks like depends mostly on the applied
CSS rather than on the HTML code. The Python documentation
http://docs.python.org/ looks much better than the (oldish) docutils web
pages. The document is called "specification" because it is indeed the
specification. Other documents target the end user, the quickref for
example: http://docutils.sourceforge.net/docs/user/rst/quickref.html

However, this was not a criticism of the choice of using asciidoc, which
may be better suited to the use case. I just wonted to provide my
opinion on readability.

Cheers,
Daniele



  reply	other threads:[~2012-08-12 23:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-11  7:46 [Xenomai] Using asciidoc for README.INSTALL Gilles Chanteperdrix
2012-08-11  8:07 ` Philippe Gerum
2012-08-11  8:54   ` Gilles Chanteperdrix
2012-08-12 22:09 ` Daniele Nicolodi
2012-08-12 22:56   ` Gilles Chanteperdrix
2012-08-12 23:08     ` Daniele Nicolodi [this message]
2012-08-12 23:51       ` Gilles Chanteperdrix
2012-08-16 20:51 ` Gilles Chanteperdrix
2012-08-20 21:00 ` Gilles Chanteperdrix

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=50283788.8040802@grinta.net \
    --to=daniele@grinta.net \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.