qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: G 3 <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Qemu-devel] Poll on QEMU documentation project
Date: Wed, 1 Feb 2017 15:17:44 -0800	[thread overview]
Message-ID: <97ae663a-f2d1-c45d-bb8d-8be352d8f84c@redhat.com> (raw)
In-Reply-To: <58763C1D-20EB-4C1F-86EC-C9903F87BDB3@gmail.com>



On 01/02/2017 14:50, G 3 wrote:
> I was thinking maybe we should add Rich Text Format, or maybe even a
> word processing format like OpenOffice, or Microsoft Word to the list of
> possible formats. These formats are super easy to use. No formatting
> rules to have to learn. All the user needs to do is just type up their
> contribute to the documentation in a word processor. The word processor
> would do all the formatting work. Tables, links, stylized text are all
> possible. This would allow us to export to other formats like HTML, PDF,
> and ascii text.

That's exactly what we _don't_ want.

We need documentation to be consistent.  RTF, OpenOffice, etc. are
presentation-based format (or at least 99% users use them as such), and
this automatically disqualifies them.  We don't want our documentation
to be a mixture of Arial, Times New Roman and Comic Sans depending on
the user that's contributing.  Besides, conversion of word processor
documents to HTML usually looks terrible.

The requirements for the format are:

* support for HTML and man as output formats, optionally PDF and text
* support for QEMU's usual submission workflow
* producing documentation with a consistent look
* tool support and extensibility
* being easy to use and not too obscure

in this order.  Based on this, the only formats we could plausibly use
are Texinfo (if only because that's what we use now), Markdown,
restructuredText, Docbook and Asciidoc.  The poll mentioned all of these
except Asciidoc, plus LaTeX as a "control group".

Paolo

  reply	other threads:[~2017-02-01 23:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.205.1485450031.31314.qemu-devel@nongnu.org>
2017-01-26 17:28 ` [Qemu-devel] Qemu-devel] Poll on QEMU documentation project G 3
2017-01-26 17:30   ` Paolo Bonzini
2017-01-26 17:40     ` G 3
2017-01-26 17:52       ` Paolo Bonzini
2017-01-26 17:57         ` Peter Maydell
2017-01-27  6:51           ` Markus Armbruster
2017-01-27 10:08             ` Peter Maydell
2017-01-30 14:21               ` Stefan Hajnoczi
2017-01-30 15:02                 ` Markus Armbruster
2017-02-01 22:50       ` G 3
2017-02-01 23:17         ` Paolo Bonzini [this message]
2017-02-01 23:36           ` G 3
2017-02-01 23:50             ` Paolo Bonzini
2017-01-26 17:58     ` Cornelia Huck

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=97ae663a-f2d1-c45d-bb8d-8be352d8f84c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).