Re: [PATCH] CodingStyle: Inclusive Terminology

From: Daniel Palmer <daniel@0x0f.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Dan Williams <dan.j.williams@intel.com>,
	torvalds@linux-foundation.org, Jonathan Corbet <corbet@lwn.net>,
	Kees Cook <keescook@chromium.org>, Chris Mason <clm@fb.clm>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	ksummit-discuss@lists.linuxfoundation.org,
	tech-board-discuss@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CodingStyle: Inclusive Terminology
Date: Mon, 6 Jul 2020 12:13:21 +0900	[thread overview]
Message-ID: <CAFr9PXnr0R71_o_0-Xmw0tcN9UUTMu1ahgp3ig5kE0LG=6N5WA@mail.gmail.com> (raw)
In-Reply-To: <20200705045505.GA2962@1wt.eu>

Hi Willy,

On Sun, 5 Jul 2020 at 13:55, Willy Tarreau <w@1wt.eu> wrote:

> I'm personally thinking that for a non-native speaker it's already
> difficult to find the best term to describe something,

I'm a nobody in the kernel world but this point made me think.

I'm a native English speaker but I don't live in an English speaking
place and my experience is that a lot of technology terms have been
directly imported from English into the local language almost as-is.

In my case master/slave have been directly transliterated into
Japanese as masuta and sureebu and exists like that in technical
documentation for example:
https://www.analog.com/jp/analog-dialogue/articles/introduction-to-spi-interface.html#

I can imagine that by changing terminology that has been in use for so
long that it's been imported into other languages directly or is
common enough that non-native speakers know what it means might have
exactly the opposite result by excluding people that aren't native
English speakers and can't decode synonyms that are obvious to a
native speaker.

Cheers,

Daniel