From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751706AbcBKPSQ (ORCPT ); Thu, 11 Feb 2016 10:18:16 -0500 Received: from home.keithp.com ([63.227.221.253]:60006 "EHLO elaine.keithp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751175AbcBKPSP (ORCPT ); Thu, 11 Feb 2016 10:18:15 -0500 From: Keith Packard To: Jonathan Corbet , Jani Nikula Cc: Daniel Vetter , linux-doc@vger.kernel.org, Linux Kernel Mailing List Subject: Re: [RFC] A first shot at asciidoc-based formatted docs In-Reply-To: <20160210135651.7dbaa1f6@lwn.net> References: <1453764522-29030-1-git-send-email-corbet@lwn.net> <20160209170938.3a4b9fb1@lwn.net> <87ziv8zmpx.fsf@intel.com> <20160210135651.7dbaa1f6@lwn.net> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Thu, 11 Feb 2016 07:18:10 -0800 Message-ID: <86si0z1djh.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 Jonathan Corbet writes: > asciidoc->HTML on its own isn't viable, I think; we do have people wanting > other formats. Though one might well ask when somebody last successfully > generated PDF...maybe it's not worth the trouble. I would like epub > someday... I'm hopeful that I can hack up asciidoc to generate usable HTML directly. Once we've got HTML, we've got epub. If we don't want to use docbook for pdf, asciidoc has a native latex backend. That's in about the same shape as the html backend. Would that be better than docbook? > There's also people who actually use the man-page output. I don't think > that should require the xml step; getting rid of that might make it > possible to do "make mandocs" and have it finish before the next merge > window opens... Adding a troff backend to asciidoc would be simple enough; I'm not sure what other method you'd suggest here. > We talked about that a bit in Geelong; the short-term idea was to generate > a TOC and use CSS to place it correctly. Daniel, if I heard you correctl= y, > you thought that would be a fine solution that would remove the need for > chunked output. Keith seemed interested in looking into this too. Here's an example that takes the docbook output with some simple CSS hacks to place the TOC alongside the document in a separate scrolling list. With a small bit of javascript, I'm pretty sure that could have collapsible entries. =2D-=20 =2Dkeith --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIVAwUBVrymMtsiGmkAAAARAQiNiw/9FKlsrJzOvPKteRU4t4FVDGqV4UbzMAin cKk3PwOyo70OB2OsJYmNZyE3jOBVzpN5S0NJg6APJ/I/93IOZJOgrM7vFdZtvCgg O4UnkyRmbTSU34DWZSpcKRcA6tSkwSQs3M1pbBpBerEeL8oanSvNzVH/4bPWmReF dr/iDarAKa4yJPYV0DpaREzHpLKwvXe6cQj4BnRvnMyT/OZiWFD7ZeT/VJQfFtbh NLGVa73hxoW76wg0582CbLEqujgpRZxnFsEoihN4lEx3/h4r5A9Uj2sFRqMUQbN/ upoY5533odDMDNUVFhkLX3w3YsfllIzLAJwPnYjZvl5PL7iu+CQo3bKz9DnC6twL +QQO54g9qzB8fnFXZi033mMZalWNEOhI9r8+Bmyk+w4EPaIu7HjlB2JFQesFhtvu Azfc+k/CtDG0zQqHf+5DKg94x9CTgcFXcQnxz6mSk2zjzqbd8V+ug3LlbZ2N0re2 Y+mOYWXDcTYjOQG4NuYAkZo/Di4+fLG0CwSH75I/p5ia1eCcCG0mhWD+PbMZ+Ywh Tx7l9x3YUazdO09TJFQrT278ELIr0PDGO2TQElZagA2UtWN3huf6A9s1/XRGiypc 3IyyP9G7/y+0yVWkiDT1djgBU1Ugn7ypz+9VtTzWOQmra54WiaBHifQJQzEkkciC pd4svqkPOTA= =D9gT -----END PGP SIGNATURE----- --=-=-=--