From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751468AbcBKPVv (ORCPT ); Thu, 11 Feb 2016 10:21:51 -0500 Received: from home.keithp.com ([63.227.221.253]:60064 "EHLO elaine.keithp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750802AbcBKPVu (ORCPT ); Thu, 11 Feb 2016 10:21:50 -0500 From: Keith Packard To: Jani Nikula , Jonathan Corbet Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Daniel Vetter Subject: Re: [RFC] A first shot at asciidoc-based formatted docs In-Reply-To: <87r3gjz7i3.fsf@intel.com> References: <1453764522-29030-1-git-send-email-corbet@lwn.net> <20160209170938.3a4b9fb1@lwn.net> <861t8k2mro.fsf@hiro.keithp.com> <87r3gjz7i3.fsf@intel.com> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Thu, 11 Feb 2016 07:21:44 -0800 Message-ID: <86pow31ddj.fsf@hiro.keithp.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Jani Nikula writes: > One of the chief complaints with the current pipeline (and some of the > proposals) has been the need to install lots of tools with lots of > dependencies. I would like to avoid the need to install bleeding edge > tools and stick to what's already widely available in distros. Thus I > would like to avoid hacking asciidoc for our needs. Agreed. That means using docbook for now; the native html output from asciidoc is simply not usable for anything more complicated than a short web page. However, getting ready to collapse the pipeline by eliminating docbook seems like a good medium-term goal. > Also, I'd really like to not have to decide between asciidoc and > asciidoctor, and only use features supported by both. Let the users pick > which one suits them better. That's harder; you'll have much different output from the two processors. I'd encourage the selection of one of these two tools instead of trying to support both. I've settled on using only asciidoc for my other projects because it doesn't require the installation of a whole new language environment. =2D-=20 =2Dkeith --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIVAwUBVrynCdsiGmkAAAARAQjFjA//TVIrVIanpVKaUQdOdDPCBgmvMA1fZd0p bCZKR8iM+vYJVJ8yZ7Q5IOh4XvPoLEIuEjXE8DyqDmOtvxAju5YoEza0argbIduZ ZvpvJvRBnisAeZbijUlebGC+q8dmGUr1J1F9BOX7lwp8QptJ5OmSANL/tFD0MOuB C8LpD3KLVL+Mk8B1S5Dl58mC09LE1KP4Uib7zzTzkLSII+IViK1HzJldnedorFSy 6RXG9b0mvTJX57Gj3qw6icarpvKpv5FjnLbaXZX5ITMSHynS7W+Y3L2ceFZif8Xp OwQ7Rp6O8REvL2h9MEq9xMFNxNeu8iWgY6g4n8mHrpMWzCOlnhhDTa59esiw1hSF XVhAZFuBuq6n2IIwQog60PAz+YiSZA3/M8ynTR+bW8rc0ATvVmBh6yfy7Utte2JF 4HPkPEQhIy9mpdKAsQyfDAWY7RfA2wOcNRQKpVZV/BnzaYdY1Y6baP2u9vMXF5H/ icVlGs8r5YD2k7PaZu6hmdtoYnOrAqNoK9Ikgf5NldbzSXUunqikg6OEyw7+7qJH gfKvDh0zouSf3MFPfTal9xRj+mB2D03OpPHneHgW+oR3BL8P9b5WAOeAUE+0U9bS Yxst08E/py2zXQGUtn50RdId1liS8MkkzWjSRGiCe5BooFFelGAp0Y9N2ltSD/7D +vUnvRPId00= =Bbpv -----END PGP SIGNATURE----- --=-=-=--