From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: Manual refactoring - Request for feedback before Buildroot Developer Days.
Date: Mon, 8 Oct 2012 14:59:35 +0000 (UTC) [thread overview]
Message-ID: <k4upon$5po$1@ger.gmane.org> (raw)
In-Reply-To: CAHXCMMLVWx3iwf0sJziz-LWDXr77biZ+c3iarcNWm7sE5wkrRQ@mail.gmail.com
On 2012-10-07, Samuel Martin <s.martin49@gmail.com> wrote:
> we will really appreciate feedback about the current manual:
>
> - what is good
Good things about the current manual:
1) It is available on line in a single HTML page. Please, please, in
the name of all that's usable, don't split it up into hundreds of
HTML pages each with few sentences sentences and the dreaded
"next, prev, up" buttons. Having it on a single page allows you
to search using the browser's "find" facility and makes it easy to
skim through to find waht you want.
2) The HTML version renders well at any window width. Some manuals
have code examples that force the the entire page to be rendered
with with a line length that's hundreds of characters long -- the
resulting pages end up being way too wide for easy use.
3) It's writtenin asciidoc.
a) Allows generation of a variety of formats (PDF, HTML, text).
b) Makes it easy to read source and submit patches.
Something like reStructuredText would also be fine. I fear
LaTeX's time has passed, and XML's time[1] has never arrived
(hopefully it never will).
[1] XML is fine as a machine-generated and machine-read format,
but no human should ever be expected to edit it except in an
emergency.
--
Grant Edwards grant.b.edwards Yow! Did YOU find a
at DIGITAL WATCH in YOUR box
gmail.com of VELVEETA?
prev parent reply other threads:[~2012-10-08 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 14:31 [Buildroot] RFC: Manual refactoring - Request for feedback before Buildroot Developer Days Samuel Martin
2012-10-08 14:59 ` Grant Edwards [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='k4upon$5po$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/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