git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitsubmodules: align html and nroff lists
Date: Wed, 1 May 2019 17:03:54 -0400	[thread overview]
Message-ID: <20190501210354.GC13372@sigill.intra.peff.net> (raw)
In-Reply-To: <20190501203216.141398-1-emilyshaffer@google.com>

On Wed, May 01, 2019 at 01:32:17PM -0700, Emily Shaffer wrote:

> There appears to be a bug in the toolchain generating manpages from
> lettered lists. When a list is enumerated with letters, the resulting
> nroff shows numbers instead. Mostly this is harmless, but in the case of
> gitsubmodules, the paragraph following the list refers back to each
> bullet by letter. As a result, reading this documentation via `man
> gitsubmodules` is hard to parse - readers must infer that a bug exists
> and a refers to 1, b refers to 2, and c refers to 3 in the list above.

Yikes, I see this, too.

> The problem specifically was introduced in ad47194; previously rather
> than generating numerated lists the bulleted area was entirely
> monospaced in HTML and shown in plaintext in nroff.

I wondered briefly if ad47194 was doing the wrong thing to convert this
section, but I think its _intent_ was right. Its author just didn't
anticipate this bug. :)

> The bug seems to exist in docbook-xml - I've reported it on May 1 via
> the docbook-apps mail list - but for now it may make more sense to just
> work around the issue.

Yeah. Specifically, the HTML generated directly from asciidoc doesn't
have this bug. Likewise, using asciidoctor has no impact (though in
theory if we eventually move to generating roff directly from
asciidoctor, the problem might go away).

I agree with you that it's worth working around in the meantime.

The patch itself looks good to me. A few observations:

>  A submodule is considered active,
>  
> -  a. if `submodule.<name>.active` is set to `true`
> +  1. if `submodule.<name>.active` is set to `true`

I'd sometimes use letters when there is already a nearby list using
numbers (and I need to be able to refer to either list distinctly). But
I checked the surrounding context and don't think that's the case here.

> -Note that (c) is a historical artefact and will be ignored if the

Not introduced by your patch, but it may be worth swapping this out for
"artifact". The spelling with the "e" is apparently a British-ism (today
I learned!), but I think we usually favor (favour!?) American spellings
in our documentation.

Obviously not super important, and definitely should be addressed in a
separate patch (if at all).

-Peff

  reply	other threads:[~2019-05-01 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 20:32 [PATCH] gitsubmodules: align html and nroff lists Emily Shaffer
2019-05-01 21:03 ` Jeff King [this message]
2019-05-20 20:54   ` Jonathan Nieder
2019-05-28 16:42     ` Junio C Hamano

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=20190501210354.GC13372@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).