mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andrei Rybak <>
To: "Martin Ågren" <>
Cc:, Junio C Hamano <>
Subject: Re: [PATCH v2] Documentation: render dash correctly
Date: Mon, 23 Jan 2023 19:52:16 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 23/01/2023 12:04, Martin Ågren wrote:
> On Mon, 23 Jan 2023 at 10:01, Andrei Rybak <> wrote:
>>   highlighted with a `$` sign; if you are trying to recreate these
>> -example by hand, do not cut and paste them---they are there
>> +example by hand, do not cut and paste them--they are there
>>   primarily to highlight extra whitespace at the end of some lines.
> OK, so this is one of the new ones compared to v1. I can see the
> argument for adding some spaces around the "--" for consistency and to
> make this a bit easier to read in the resulting manpage (which can of
> course be very subjective), but then I can also see that kind of change

There are some less subjective guidelines.  Asciidoc turns "--" into an
em-dash.[1]  In English, em-dash is almost always not surrounded by
spaces (it is in French, for example), while en-dash is spaced in
English when used instead of an em-dash.[2][3][4]

This means that it's all the other places that use " -- " with spaces
that are incorrect.



2. English Wikipedia is clear about its usage of en- and em-dashes:

3. Chicago Manual of Style FAQ doesn't spell out the spacing, but it's
    clear from examples:

4. More confirmation on English Language and Usage Q&A website on Stack
    Exchange network:

> being left out as orthogonal to this patch.

Indeed, correcting spacing around dashes is orthogonal.  Also, it might
not be very desirable to have so much churn for spacing issues.
> This v2 patch looks good to me.

Thank you for review.
> Martin

      parent reply	other threads:[~2023-01-23 18:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 16:56 [PATCH] Documentation: render dash correctly Andrei Rybak
2023-01-22 22:53 ` Junio C Hamano
2023-01-23  8:19   ` Martin Ågren
2023-01-23  9:01 ` [PATCH v2] " Andrei Rybak
2023-01-23 11:04   ` Martin Ågren
2023-01-23 17:39     ` Junio C Hamano
2023-01-23 18:52     ` Andrei Rybak [this message]

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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

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).