From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42817) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQOGG-0008QG-OK for qemu-devel@nongnu.org; Tue, 15 Nov 2011 14:01:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQOGF-0006zZ-MI for qemu-devel@nongnu.org; Tue, 15 Nov 2011 14:01:36 -0500 Received: from e4.ny.us.ibm.com ([32.97.182.144]:42225) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQOGF-0006zK-Jo for qemu-devel@nongnu.org; Tue, 15 Nov 2011 14:01:35 -0500 Received: from /spool/local by e4.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 15 Nov 2011 14:01:30 -0500 Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pAFJ0qdo312112 for ; Tue, 15 Nov 2011 14:00:52 -0500 Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pAFJ0pRj013738 for ; Tue, 15 Nov 2011 12:00:51 -0700 Message-ID: <4EC2B6E2.8010603@us.ibm.com> Date: Tue, 15 Nov 2011 13:00:50 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1321310505-27845-1-git-send-email-aliguori@us.ibm.com> <4EC222A3.9010209@redhat.com> <4EC26CB8.5020508@us.ibm.com> <4EC2AA14.3000106@weilnetz.de> In-Reply-To: <4EC2AA14.3000106@weilnetz.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/5] docs: convert specifications to markdown List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: Avi Kivity , qemu-devel@nongnu.org On 11/15/2011 12:06 PM, Stefan Weil wrote: > Am 15.11.2011 14:44, schrieb Anthony Liguori: > Markdown is nice for separated specs and README files, > but is it also possible to create a complete printed manual > from all markdown files? I think high quality information beats pretty formatting any day. The problem I see with our current documentation strategy is that it's very monolithic (one big printed manual) and it's in a format that many people consider obscure. I think small stand alone documents that are easy to author are going to result in a better end user experience than one big document with pretty formatting. Regards, Anthony Liguori > I thought of a different solution: keep qemu-doc.texi and qemu-tech.texi > and integrate texi files made from markdown files (with pandoc) into > these two documents to get complete manuals. > > Regards, > > Stefan Weil >