Small improvements to the suggested language page#79
Small improvements to the suggested language page#79abuango merged 4 commits intoinclusivenaming:mainfrom
Conversation
content/language/word-list.md
Outdated
| * Use the adjective as an entity prefix (e.g., _allowedNouns_) | ||
| * Also acceptable: allowlist, denylist, etc. |
There was a problem hiding this comment.
I agree mostly with your other suggestions, but this is relatively useless. As discussed in the other PR, such terms do more harm than good, and stating that they are "acceptable" replacements creates problems.
|
On 08/06/21 20:13, Celeste Horgan wrote:
Same comment as below – the Language workstream is re-evaluating these
suggestions and will revise the recommendations themselves shortly. I
like your revisions to the reasoning itself and would like to merge
those, however.
Fair enough, I'll revisit that after the language workstream is done.
Paolo
|
bonzini
force-pushed
the
patch-1
branch
3 times, most recently
from
bfdba2b to
4daa3d2
Compare
|
@celestehorgan any more comments on this PR or can it be merged? |
|
There are still doubts as to the technical correctness of the second paragraph. I believe we'll have to wait for the workstream to write up the recommendation regarding blacklist / whitelist prior to merging either PR related to the subject |
|
Now that the pull request has already been cut down substantially, I am not sure there's anything new on the technical side (i.e. in the second paragraph. The differences amount to:
|
|
* pointing out what is difficult to translate to other human languages
(not technical) and in your words "does more harm than good"
More information is available at https://github.com/kludge-cs/transparency/blob/main/open-statements/2021-04-04--TERMINOLOGY.md.
We do not officially have a recommendation for this yet, but we will
soon.
|
quaid
left a comment
quaid
left a comment
There was a problem hiding this comment.
This is a very good adjustment and clarification for this, I think it's ready to publish.
Languages other than English may not allow turning a noun into a verb with the same agility that English has. Some of them might not form compound words easily and resort to English loan words. In such a scenario, it would not be impossible for the translator to revert "allowlist" into a loan word based on "blacklist", because that's a more commonly known word to his audience of non-English speakers. This would make the effort to use inclusive language vain. Therefore, emphasize more the possibility to use not just the "-ed" form of verbs, but also the verbs themselves without the "list" suffix. Their past participles easily work as adjectives, and they are easily translated.
bonzini
force-pushed
the
patch-1
branch
2 times, most recently
from
7d025d3 to
563785d
Compare
…ustry This origin is not substantiated by sources such as the Oxford English Dictionary. The more likely origin seem to be in politics, where it was applied to people, with the term's surge in popularity occurring during World War I. At the time, "blacklist" was used for the list of firms denied access to various Entente infrastructure in the United Kingdom. During and after World War II, the term started being used to describe various kinds of restrictions, generally not limited to the publishing industry. See also: https://books.google.com/ngrams/graph?content=blacklist&year_start=1800&year_end=2000 I tried keeping the reference to slavery, but I couldn't fit it in the rest of the text which talked about the different metaphors behind colors in various cultures.
|
@quaid I have rebased. |
6 participants
This pull request contains a mix of changes to the suggested language page. Each change is separated into its own commit.
The change to the suggestions for whitelist/blacklist is similar in spirit to #45.