git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Shourya Shukla <shouryashukla.oo@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH v4 4/4] gitfaq: fetching and pulling a repository
Date: Sat, 02 May 2020 18:03:26 -0700	[thread overview]
Message-ID: <xmqqftchkext.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CABPp-BGrsw1V3gUWN40DTRCPBD5ZD5kvoqdjMuEJtJKCni09_w@mail.gmail.com> (Elijah Newren's message of "Sat, 2 May 2020 12:00:36 -0700")

Elijah Newren <newren@gmail.com> writes:

>> Also, a nit but, we are supposed to use 1 SP or 2 SP after a full
>> stop(.)? In India we use 1 SP, is it different in other countries?
>
> Ah, the never ending spacing debate...
>
> There may be variation country-to-country, but I doubt it's country
> specific.  It's more a raging debate based on the fact that "official"
> rules have changed multiple times, old habits die hard, different
> contexts exist for different audiences, and various other wrinkles.

https://www.theverge.com/2020/4/24/21234170 ;-)

Since very old days of print media until now and well into the
future, readers want to see longer whitespace after the end of each
sentence than whitespace between words.  Behaviour of programs that
that take your "text file" as its input and produces rendered output
differ.  Some ignore the number of spaces after the full-stop and
"do the right thing" its output (that's the norm for typesetting
systems), and others want to see only one space there, and leaves
more swhitespace than optimal if you put two or more (which is often
how WYSIWYG word processors work).

The ideal would be to keep both the source text file and rendered
output pleasant to the eyes, and that means we type two spaces after
the end of a sentence in the source (which is meant to be read in
monospace text) and we avoid formatting programs that break (i.e.
produce more spaces than desirable) when fed more than one space
after each sentence (otherwise, we would be forced to use only one
space and hurt our eyes).

I think our arrangement to go from source text through AsciiDoc or
Asciidoctor to manpage or XHTML produces the right output with two
spaces, so we are good.

  reply	other threads:[~2020-05-03  1:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  9:38 [PATCH v4 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
2020-04-29  9:38 ` [PATCH v4 2/4] gitfaq: changing the remote of a repository Shourya Shukla
2020-04-29 16:17   ` Elijah Newren
2020-04-29 17:01   ` Junio C Hamano
2020-04-29  9:38 ` [PATCH v4 3/4] gitfaq: shallow cloning " Shourya Shukla
2020-04-29 16:00   ` Elijah Newren
2020-05-02  5:00     ` Shourya Shukla
2020-04-29 17:09   ` Junio C Hamano
2020-05-02  6:13     ` Shourya Shukla
2020-05-04 16:06       ` Junio C Hamano
2020-05-05 12:26         ` Derrick Stolee
2021-05-06  2:49           ` dyrone teng
2020-04-29  9:38 ` [PATCH v4 4/4] gitfaq: fetching and pulling " Shourya Shukla
2020-04-29 15:56   ` Elijah Newren
2020-04-29 17:19     ` Junio C Hamano
2020-05-02  6:57     ` Shourya Shukla
2020-05-02 19:00       ` Elijah Newren
2020-05-03  1:03         ` Junio C Hamano [this message]
2020-04-29 16:16 ` [PATCH v4 1/4] gitfaq: files in .gitignore are tracked Elijah Newren
2020-05-02  6:36   ` Shourya Shukla
2020-04-29 16:55 ` 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=xmqqftchkext.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    --cc=shouryashukla.oo@gmail.com \
    /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).