git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Merlin (they / them) Patterson" <merlinpatt@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	"Merlin (they/them) via GitGitGadget" <gitgitgadget@gmail.com>,
	git@vger.kernel.org,
	"Merlin (they/them)" <merlinpatt+githubgit@gmail.com>
Subject: Re: [PATCH] docs: update coding guidelines to be more inclusive
Date: Sun, 20 Feb 2022 21:23:32 +0000	[thread overview]
Message-ID: <YhKxVBReUMJUB0tw@camp.crustytoothpaste.net> (raw)
In-Reply-To: <220219.8635kfhfoy.gmgdl@evledraar.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3881 bytes --]

On 2022-02-18 at 23:18:35, Ævar Arnfjörð Bjarmason wrote:
> I think this came about because of a previous discussion that you'll
> find in the list archive where some native speakers were maintaining
> that "they" in this context was widely accepted usage because it had
> made it into some style guides single-digit years ago.

Singular they has been in common use for centuries.  It became less
common for many years because prescriptivists proposed using "he" to
refer to people of all genders, which was in common use for a long time,
until it was widely criticized as being sexist (and also, at times,
sounding bizarre).  "He or she" was then used in formal writing, but
that was also criticized as not being inclusive as well as being wordy
and awkward.  During this entire time, singular they has remained in
common use in speech and informal writing and is widely recognized as
part of the English language.

It's true that it is only now becoming more acceptable in formal
writing, but it is well known and commonly used in English as a whole
and has been for a long time.

I will also freely admit that for people who have learned English as a
second language sometime in the past, this would probably not have been
covered in the textbook.  As I continue to use Spanish, I learn things
about the language and how it's used today that differ from what I
learned when I started learning it formally over two decades ago, and
that's okay. Language evolves and as speakers of a second or third
language, we'll have to evolve with it.

> I.e. this was a perhaps flawed attempt to say something like "this
> phrasing sounds weird, but it's actually correct".
> 
> As someone who speaks at least 4 languages regularly with levels of
> proficiency ranging from native to something that sound as though I'm
> trying to butcher the language, I can assure you that advice like that
> *is* really useful to a non-native speaker.

I agree, this context would be helpful.  Maybe, if we retain this, we
can just explicitly say, "Even though some non-native speakers may find
the use of singular they unusual, it is in fact common in English and
preferred in our documentation."

> I.e. whatever you or anyone else thinks about this usage of "they" it
> *is* relatively obscure usage of English. I'd even bet that for some
> readers of this document it's the first time they've ever seen it.

It is simply not the case that this is obscure.  As I've said in the
past, singular they, in the sense of referring to a single person whose
gender is unknown or irrelevant, has been in use since the 14th century
and has been used by William Shakespeare, Lord Byron, and Jane Austen.
It is routinely used for this purpose by fluent non-native speakers as
well (I have noted colleagues doing this).

I will admit that using they as the pronoun for a person whose gender is
known and who has explicitly requested the use of this pronoun is much
more recent, which probably dates to the mid 20th century (albeit at a
much lower frequency than today), but this is not the context in which
we are using the pronoun in our documentation.

It may be that for some readers it is the first time they've seen it,
but it will be far from the last if they continue to read English.
Understanding the main idea of a technical document in one's specialized
field (e.g., the Git documentation) is part of the CEFR B2 level, and at
that point, I'd expect the reader to have read numerous news articles
and online documents where this usage is common or becoming so.

As to your suggestion to this effect, I should point out that I'm fine
with removing this text from the documentation, as you suggested,
provided we can stop having extended debates about it on the list.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2022-02-20 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 16:34 [PATCH] docs: update coding guidelines to be more inclusive Merlin (they/them) via GitGitGadget
2022-02-16 22:12 ` Junio C Hamano
2022-02-17 10:02   ` Ævar Arnfjörð Bjarmason
2022-02-18  3:02     ` Junio C Hamano
     [not found]       ` <CAFZ26y3re+fJapXzLOpf73F-ECXhg2sCoBtm_=VUFy5nbN2UVQ@mail.gmail.com>
2022-02-18 23:18         ` Ævar Arnfjörð Bjarmason
2022-02-20 21:23           ` brian m. carlson [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:
  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=YhKxVBReUMJUB0tw@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=merlinpatt+githubgit@gmail.com \
    --cc=merlinpatt@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).