From: "Đoàn Trần Công Danh" <email@example.com> To: Bagas Sanjaya <firstname.lastname@example.org> Cc: Git Users <email@example.com> Subject: Re: [RFC suggestion] Generate manpage directly with Asciidoctor Date: Fri, 7 May 2021 19:27:10 +0700 [thread overview] Message-ID: <YJUyHkYAIth0W9dY@danh.dev> (raw) In-Reply-To: <firstname.lastname@example.org> On 2021-05-07 13:06:31+0700, Bagas Sanjaya <email@example.com> wrote: > Hi, > > Asciidoctor has support for directly generating manpage, see . While I'm impressed with this news. > 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). I'm pretty sure xmlto doesn't depend on dblatex and/or texlive. I'm building Git and Git's documentation on different Linux boxes with asciidoc, most of them don't have dblatex and/or texlive. In fact, I only have texlive installed in my laptop. I guess you're using Debian or one of its derived distribution? Debian puts dblatex as xmlto's rec.  I think you can use: apt install --no-install-recommends xmlto to avoid those recommendations. > So completely migrating to Asciidoctor can eliminate xmlto requirement > for generating manpage. > > What do you think about above? Hm, I'm pretty sure Ruby (asciidoctor's language) is very hard to port. Last I heard, it's buggy on some platforms. I think we're better to do like this: * If we're using asciidoc, we will use xmlto * If we're using asciidoctor, we will generate man-pages with asciidoctor directly > : https://docs.asciidoctor.org/asciidoctor/latest/manpage-backend/ : https://packages.debian.org/sid/xmlto -- Danh
next prev parent reply other threads:[~2021-05-07 12:27 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 [this message] 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 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=YJUyHkYAIth0W9dY@danh.dev \ --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).