git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: [RFC/NOPATCHv3 1/4] doc: add an option to have Asciidoctor build man pages directly

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Jun 18, 2021, 20:57 UTC
Message-ID
<60cd08a716873_c0ff9208c4@natae.notmuch>
In-Reply-To
<20210618203057.790320-2-felipe.contreras@gmail.com>
Felipe Contreras wrote:
Show 8 quoted lines
> From: "brian m. carlson" <sandals@crustytoothpaste.net>
> 
> Asciidoctor contains a converter to generate man pages.  In some
> environments, where building only the manual pages and not the other
> documentation is desired, installing a toolchain for building
> DocBook-based manual pages may be burdensome, and using Asciidoctor
> directly may be easier, so let's add an option to build manual pages
> using Asciidoctor without the DocBook toolchain.
This suffices:
  There's no need to use xmlto to build the man pages when modern
  asciidoctor can do it by itself.
> We generally require Asciidoctor 1.5, but versions before 1.5.3 didn't
> contain proper handling of the apostrophe, which is controlled normally
> by the GNU_ROFF option.
This isn't true. There's no difference from 1.5, 1.5.3, 2.0.0 or even 2.0.15.

The only fix regarding apostrophes was done by me [1], it's in the master branch, but not in any release yet.

> This option for the DocBook toolchain, as well
> as newer versions of Asciidoctor, makes groff output an ASCII apostrophe
> instead of a Unicode apostrophe in text, so as to make copy and pasting
> commands easier.

That isn't true. GNU_ROFF is only for docbook and doesn't affect asciidoctor in any way.

> These newer versions of Asciidoctor (1.5.3 and above)
> detect groff and do the right thing in all cases, so the GNU_ROFF option
> is obsolete in this case.

Not true. There's nothing in 1.5.3 or any version that detects groff, or have anything to do with GNU_ROFF.

> Because Asciidoctor versions before 2.0 had a few problems with man page
> output, let's default this to off for now, since some common distros are
> still on 1.5.

There's nothing from 1.5.8 to 2.0.0 that should be of interest to the git project.

What are these "few problems"?

The diff is correct, but 1) the original patch was done by me, and 2) I already have the exact same version here [2].

Cheers.

[1] https://github.com/asciidoctor/asciidoctor/commit/af0ef59538fccfbdec053b82e102a240b15cdda6 [2] https://lore.kernel.org/git/20210521224452.530852-4-felipe.contreras@gmail.com/

-- 
Felipe Contreras
Previous: Felipe ContrerasNext: Felipe Contreras
Message 5 of 9 in “[RFC/NOPATCHv3 0/4] doc: asciidoctor: direct man page creation and fixes (brian's version)”
  1. Felipe ContrerasJun 18, 2021
  2. 2/4 doc: add linkgit macros for asciidoctorFelipe Contreras, Jun 18, 2021
  3. Felipe ContrerasJun 18, 2021
  4. 1/4 doc: add an option to have Asciidoctor build man pages directlyFelipe Contreras, Jun 18, 2021
  5. Felipe ContrerasJun 18, 2021
  6. 3/4 doc: use XML-style escapes only for HTML and XMLFelipe Contreras, Jun 18, 2021
  7. Felipe ContrerasJun 18, 2021
  8. 4/4 doc: remove GNU_ROFF optionFelipe Contreras, Jun 18, 2021
  9. Felipe ContrerasJun 18, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.