retextjs / retext-equality Goto Github PK
View Code? Open in Web Editor NEWplugin to check for possible insensitive, inconsiderate language
Home Page: https://unifiedjs.com
License: MIT License
plugin to check for possible insensitive, inconsiderate language
Home Page: https://unifiedjs.com
License: MIT License
Currently the word "mental" is flagged as inconsiderate in the context of the phrase "mental health".
When used in the harmless contexts of the phrase "mental health", the word "mental" should not be flagged.
The word "mental" is flagged as inappropriate.
Hi team, I've been using your repo, it's great. But with the latest release of 3.9.0 I'm getting an npm error now (see error below). It looks like index.js in lib still requires it, but the patterns.json file no longer exists.
Error: Cannot find module './patterns.json'
I'd like to continue to use this, so hopefully you can fix this issue soon :)
Best,
Derek
Commit 1585a36 changed the sample prose in the usage example to this sentence:
He’s pretty set on beating your butt for sheriff.
But it didn't adjust the output to match. As a result, the sample output:
example.txt 1:1-1:4 warning `His` may be insensitive, use `Their`, `Theirs`, `Them` instead her-him retext-equality 1:31-1:37 warning `master` / `slave` may be insensitive, use `primary` / `replica` instead master-slave retext-equality ⚠ 2 warnings
contains admonishments about language (master
, slave
) that doesn't appear anywhere in the input text.
Hi! Is it within the scope of this package to include screening for phrases similar to "make America great again," which is a political slogan? It is problematic to many groups that this library tries to help prevent insensitive language towards. Unfortunately it shows up in a lot of things as a joke, since it's an easy play on words, but it's pretty hurtful to some people. Sources: one and two
Thoughts? Ideally something like this would be a regex-type match of anything like "make ___ great again" but I don't see that kind of match in any of the other examples. Possibly checking for "great again" would be enough. I haven't thought of any false positives that don't sound like a reference to the phrase.
I am happy to PR this if you think it's within scope and agree that "great again" is a reasonable search term. Thank you!
Suggest spree
, other things (?) instead of binge
binge
might be insensitive towards folks with eating disorders
🤷♂️
Suggested over email
e.g., not add
but ADD
Related to GH-31.
Probably, retext-profanity, when it exists. EDIT: https://github.com/wooorm/retext-profanities
This is insane.
Insanity is a serious condition and could be better written using other words.
Read more here: http://whatprivilege.com/replacing-crazy-for-ableism-and-preciseness-of-language/ (also some more words we could add there, and some good discussion in the comments)
I need some help on where to get started with integrating the Spanish wordlist from words/cuss
. If anyone has a hint or idea of where to get started, that would be greatly appreciated :)
Like most words in the condescending list
straight-forward adds little to a sentence.
Often a sentence containing it can be deleted without lose of value.
The method straight-forward.
The FooBar algorithm is straight-forward.
You can follow the straight-forward steps to solve your problem.
It is somewhat like just and easy which are on that list.
Add straight-forward to condescending list.
Don't add straight-forward
to condescending list.
Maybe it isn't a great fit.
Hey there! I am working on adding some notes for LGBTQ+ terms (and one ablist note) and I had two questions.
Do I need to add notes to the tests somewhere?
In this test, if I am changing the note to be an actual description, does this test need to be replicated somewhere else?
t.same(
retext()
.use(equality)
.processSync(doc).messages[0].note,
'If possible, describe exacly what this is. (source: http://ncdj.org/style-guide/)',
'should patch `description` when applicable'
)
Once I get some answers and have committed a few rules/notes, I'd love to help get a document set up about contributing, if that would be helpful!
Thanks!
This project does not include racially insensitive words for white people.
Add the word "Cracker" as an offensive word.
Acknowledge that this is an incomplete project if you work in countries with a white-minority population on the README.md
I don't have a better suggestion, but "native land" feels like a potentially problematic suggestion to be recommending to people whose families may not be from the indigenous peoples of their home country. See https://native-land.ca/
These terms are considered by professional Anthropologists to be racially charged, derogatory and harmful to the welfare of indigenous groups. The Association of Social Anthropologists issued a statement that reads:
'All anthropologists would agree that the negative use of the terms 'primitive' and 'Stone Age' to describe [indigenous peoples] has serious implications for their welfare. Governments and other social groups. . . have long used these ideas as a pretext for depriving such peoples of land and other resources.'
Similarly, a major NGO dedicated to supporting endangered indigenous groups, Survival International writes:
Terms like 'stone age' and 'primitive' have been used to describe tribal people since the colonial era, reinforcing the idea that they have not changed over time and that they are backward. This idea is both incorrect and very dangerous. It is incorrect because all societies adapt and change, and it is dangerous because it is often used to justify the persecution or forced 'development' of tribal peoples. The results are almost always catastrophic: poverty, alcoholism, prostitution, disease and death.
Could it be something like these, below?
- type: simple
note: Replace racist language about indigenous peoples with more accurate and inclusive words
considerate:
- simple
- indigenous
- hunter-gatherer
inconsiderate:
- primitive
- savage
- stone age
- type: simple
note: Replace racist language about indigenous peoples with more accurate and inclusive words
considerate:
- society
- community
inconsiderate:
- tribe
I'm not sure about this next one, is this a good way to do it?
- type: simple
note: Replace racist language about indigenous peoples with more accurate and inclusive words
considerate:
- complex culture
- complex technology
inconsiderate:
- sophisticated culture
- sophisticated technology
What do you think?
Seems like man
is missing from gals-men
, woman
is picked up, but man
is not.
Tell us how to reproduce this issue. Please provide a working and simplified example.
🎉 BONUS POINTS for creating a minimal reproduction and uploading it to GitHub. This will get you the fastest support. 🎉
In the lines here, "ladylike" and "like a man" are said to be inconsiderate, which totally makes sense.
However, the suggestions to fix these words are completely outrageous. Why on earth does a program that is made to promote equality for everyone contain suggestions that "ladylike" should be replaced with "cultured"? Is this some sort of subversive way to suggest that ladies should be cultured?
This problem also exists with the "like a man" suggesting "bravely". Is the program implying that men should be brave?
I just thought I'd bring this point to attention as these suggestions really seem to lower the quality of the program and may make people think that the program is not actually promoting social equality :)
Not sure if it belongs in this retext, but I find that terms like "obviously" and "everyone knows" to be insensitive and inconsiderate.
Couple more ideas here:
https://css-tricks.com/words-avoid-educational-writing/
"Autistic" is a valid way to refer to a person with autism and should be preferred to "person with autism spectrum disorder", not the other way around. Autism is a disability, not a mental disorder.
Some additions from this list that I didn't see in the rules. Sorry if I missed any!
https://www.autistichoya.com/p/ableist-words-and-terms-to-avoid.html
No one person can belong to all racial groups.
This means that no one person can objectively determine how offensive a word is.
Tier ranking how offensive one racial epithet over another seems like a slippery slope to the type of problem this project purports to be trying to solve
All racial epithets should be in this package. They're an equality issue, not a profanity issue. They should all be considered at the same level and as one evil.
Write supporting documentation which details the thought process behind the tier ranking of each racial epithet. I suspect this won't be pretty.
Ask Peter to review this and ask him what he thinks about it.
This currently warns on him
and he
, but I'm writing about a specific person, so gender does matter.
I have followed each of @Murderlon's suggestions whilst trying to contribute to this project.
This project is downloaded by 20,000 people a week who are actively working to try and improve their use of language.
This project, according to @Murderlons comment in #118, contains only words which are "inconsiderate but is not necessarily considered profane"
This project considers "sand niggers" to be a lesser insult than "cracker" by including it only in this project and not in the profanities project.
The use of the phrase "sand niggers" is explicitly illegal in the United Kingdom and would therefore clearly be better suited to the profanity project. This is also true of the other racial epithets in this project.
@Murderlon has said that his rationale for this is so obvious that he doesn't have to explain it. Given the illegality of the words used in this project I cannot see that it is that obvious.
One might also think that if the true aim of this project was to improve the language used by people who download it then a discussion (not the immediate closure of issues) followed by an explanation might move not only the project, but the aims of the project as a whole, in the right direction.
I would like to invite @Murderlon to join a call with me and some friends from the Muslim Council of Britain to see if we can correct his thinking.
Accept responsibility
Acknowledge failure
In #122 @Murderlon makes the suggestion that anti-arab racism is not illegal in and of itself in the United Kingdom. "Sand nigger" is not dealt with as the concatenation of the word "sand" with an actual offensive term. It is an offensive term that has legal consequences all of it's own.
If the legality of a word determines which repo it sits within then this project should retain legal counsel in each country it intends to support -- if only to ensure the package is accurate.
@Murderlon, a software engineer, is not a lawyer and is making decisions that make absolutely zero logical sense in this regard.
Despite acknowledging that this project should accept input, discuss it, and try to move towards better language for all he then immediately closes the issue.
The level of effort being put in to stop insults towards Arabs being treated the same as insults towards white people is concerning. Thusly, I have reported this project to both npm
and GitHub
for violating community guidelines.
This entire mess is a really good example of why this project perhaps doesn't make sense at all.
Retain counsel in every country this project aims to support if you're making decisions based on legality. Software engineers are NOT lawyers.
Stop running the project. Inaccuracies on the issue of racism are worse than the project not existing at all. This could very easily result in an increase in using of "sand niggers" as it is a lesser problem according to the linter... almost making it acceptable to some people, much like a compiler warning vs an error.
Discuss things in issues, don't just close them
Acknowledge that the issues this repo attempts to solve are socio-cultural.
Acknowledge that software engineers are famously not the right people to solve socio-cultural problems.
Acknowledge that people who cannot accept constructive criticism on socio-cultural issues should not be running projects which aim to improve socio-cultural problems.
@Murderlon has asked me to re-open this issue as it covers a specific term that can be rectified. He outlines his reasoning for this in #119.
No one person can belong to all racial groups.
This means that no one person can objectively determine how offensive a word is.
Tier ranking how offensive one racial epithet over another seems like a slippery slope to the type of problem this project purports to be trying to solve.
If sand nigger
is appropriate here, so is cracker
.
Without making a judgement on the validity of peoples hurt feelings we cannot come up with a reason for why one is here and another isn't.
Add cracker
to this repo
Remove sand nigger
from this repo
I am supporting a colleague's project to build a browser plugin for encouraging gender-neutral language in German. I was really happy to find retext-equality
and think it could be a brilliant base for some of the functionality.
I want to support my colleague in adding German language to retext-equality
. (Some of the contributors won't be familiar with programming and I don't speak German.) I have seen that there are similar approaches to support retext-profanities
(get-alex/alex#212). I also found a relevant issue here which ended with @wooorm refactoring the code to support multiple languages (#59). This is great!
I've started following the suggestions in #59 (comment) by adding a couple of basic rules and I am now trying to add the tests. I have a few questions about the best way to do this as it will form the template for both German and adding other languages.
Should I follow the approach taken in retext-profanities
and export retextEqualityDe
from de.js
?
How should I set up tests?
I'm not super familiar with writing tests in Javascript but it looks simple enough. That said, I would like some support in creating a template for testing non-English language patterns in retext-equality
.
The main reference I have found is that retext-profanities
has the following test (https://github.com/retextjs/retext-profanities/blob/main/test.js#L35):
const fileFr = await retext().use(retextProfanitiesFrench).process('Merde!')
assert.deepEqual(
fileFr.messages.map(String),
['1:1-1:6: Don’t use `Merde`, it’s profane'],
'should support other languages'
)
This only runs for one test, whereas in retext-equality
there are many tests for English.
Could someone give me an example of how a good template for the non-English tests would look?
I could intuitively push forward or not put in tests but I don't think either are good ideas!
Originally “he’ll” slips through
on get-alex/atom-linter-alex#14.
The term 'sophisticated technology' describes advanced technology. As a person not deeply involved into sensitive language, I don't know what's wrong about that term, as it doesn't describe a group of people but rather technical things like machines or inventions.
Could you perhaps add an explanation to that entry in race.yml
, so that I can make an informed decision whether using the word 'sophisticated' is OK in a certain context? At least, https://en.wiktionary.org/wiki/sophisticated#English doesn't generally describe the word as discouraged, it lists an obsolete meaning that might have caused this word to appear in the list of racial words.
Leave the users (especially nonnative speakers who may only know the primary meaning of the word) unclear about the decision to include the word in the list of racial words.
Currently, she and him
is not warned about because both “categories” are close to each other.
There is a use case to still warn about it, and suggest them
regardless.
The word list at https://github.com/retextjs/retext-equality/blob/master/script/press.yml contains an extra empty entry at the very last line, that is converted to null
during parsing, and then to the string "null"
somewhere further down the pipeline, leading to the word "null" being considered insensitive.
6.2.0
No response
See the discussion from January. As it is now, this library replaces the word "Mexican" in a phrase such as "Mexican Indie Rock" with "Latinx". The rule behind this suggests that "Latino" and "Latina" should be replaced with the "gender inclusive" word "Latinx".
I'm not here to discuss the acceptability of Latinx over Latino and Latina. Instead I'd like to ask why "Mexican" should be included as a target for replacement following this rule.
I understand that the current rule that favors "Latinx" over "Mexican" was probably written to prevent English speakers from using "Mexican" to refer to people from South or Central America. However, that is:
If I understand the discussion started by @metaverde, that user actually seems to suggest this project implements a rule like this:
- type: basic
note: Avoid describing Indigenous people in terms of their colonizers.
considerate:
- people from Mexico, South America, or Central America
inconsiderate:
- latino
- latina
- latinx
In their view, "Latinx" actually is "describing Indigenous people in terms of their colonizers". So, I can imagine they were a bit shocked when this project suggests the opposite, to replace "Mexican" with "Latinx". The user didn't seem to see any issue with the stated goal of the rule, to prevent gendered language. In any case, I'll open a pull request #114 to simply drop Mexican from the "inconsiderate" words that trigger that gender-neutral rule.
As for the other suggested rule, I for now would advise this project avoids pitting words like "Mexican" and "Latinx" against each other. The Washington Post Article cited by the user @metaverde in the discussion is more about the gender-neutral language issue than on the acceptability of common terms like "Hispanic" or "Latino".
"Mexican Indie Rock," as well as most uses of the word "Mexican," should not be flagged as offensive.
"Mexican Indie Rock" is flagged as offensive.
Node v16
yarn v2
macOS
No response
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.