From: "brian m. carlson" <firstname.lastname@example.org> To: Bagas Sanjaya <email@example.com> Cc: Git Users <firstname.lastname@example.org> Subject: Re: [RFC suggestion] Generate manpage directly with Asciidoctor Date: Fri, 7 May 2021 20:25:36 +0000 [thread overview] Message-ID: <YJWiQH2nf0B14Zy7@camp.crustytoothpaste.net> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1374 bytes --] On 2021-05-07 at 06:06:31, Bagas Sanjaya wrote: > Hi, > > Asciidoctor has support for directly generating manpage, see . > > We support using Asciidoctor as drop-in replacement for original > Asciidoc, but currently we need to use xmlto together with Asciidoc(tor) > to produce manpages. However, most users don't inclined to install > xmlto toolchain, partly because they had to download more than 300 MB > of data just to install xmlto and its dependencies (including dblatex > and texlive). If you're installing on Debian, you want to install with --no-install-recommends to avoid the dependency on dblatex or fop, libpaper-utils, and zip. That should avoid the large downloads. > So completely migrating to Asciidoctor can eliminate xmlto requirement > for generating manpage. > > What do you think about above? I didn't do this because it makes things very complicated in the Makefile and my goal was to minimize the needed changes and divergence. I'm not opposed to someone else doing it, but I expect it will be a bunch of work. It also doesn't help if you're generating more than just the manual pages, since generating the PDFs will definitely require xmlto and either dblatex or fop. I personally prefer fop over dblatex, but folks have different opinions. -- brian m. carlson (he/him or they/them) Houston, Texas, US [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2021-05-07 20:25 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-07 6:06 Bagas Sanjaya 2021-05-07 12:02 ` Randall S. Becker 2021-05-07 22:55 ` Felipe Contreras 2021-05-07 22:57 ` brian m. carlson 2021-05-08 1:42 ` Randall S. Becker 2021-05-07 12:27 ` Đoàn Trần Công Danh 2021-05-07 12:47 ` Bagas Sanjaya 2021-05-07 23:03 ` Felipe Contreras 2021-05-08 4:27 ` Bagas Sanjaya 2021-05-07 20:25 ` brian m. carlson [this message] 2021-05-07 22:19 ` Jeff King 2021-05-08 4:22 ` Bagas Sanjaya 2021-05-09 8:20 ` Martin Ågren 2021-05-09 18:46 ` Felipe Contreras 2021-05-10 18:43 ` Martin Ågren 2021-05-10 22:24 ` Jeff King 2021-05-11 4:27 ` Felipe Contreras 2021-05-11 6:13 ` Jeff King 2021-05-11 8:03 ` Felipe Contreras 2021-05-11 12:44 ` Ævar Arnfjörð Bjarmason 2021-05-11 19:00 ` Felipe Contreras 2021-05-11 19:09 ` Jeff King 2021-05-11 20:22 ` Felipe Contreras 2021-05-11 23:14 ` brian m. carlson 2021-05-12 1:44 ` Felipe Contreras 2021-05-11 18:45 ` Martin Ågren 2021-05-11 19:07 ` Jeff King 2021-05-11 19:11 ` Martin Ågren 2021-05-11 20:14 ` Felipe Contreras 2021-05-11 9:04 ` Jean-Noël Avila 2021-05-11 18:54 ` Martin Ågren 2021-05-07 23:35 ` Felipe Contreras 2021-05-07 23:57 ` brian m. carlson 2021-05-08 3:10 ` Jeff King 2021-05-08 3:23 ` Jeff King 2021-05-09 0:22 ` brian m. carlson 2021-05-09 8:29 ` Martin Ågren 2021-05-07 22:48 ` Felipe Contreras
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YJWiQH2nf0B14Zy7@camp.crustytoothpaste.net \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [RFC suggestion] Generate manpage directly with Asciidoctor' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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 read-only IMAP folder(s) and NNTP newsgroup(s).