-
-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More Helpful Response to He/Her Pronouns #297
Comments
Hi @iankolaja! You are right! And there are other words too: lots of disabled folks want to be disabled instead of person with a disability. This project was made for technical documentation. For readmes. Where the main problem is folks using he for users, where stereotypes are too prevalent. |
Hi all! My partner and I have been designing a solution for advanced behavior and functionality for She/Her pronouns. We are claiming this task. |
Subject of the feature
Using pronouns should give an occasional reminder to ensure that the pronouns they are using are appropriate for the person being addressed.
Problem
Currently, people are told that their use of the "he/him/his" and "she/her/hers" pronouns could be insensitive if this rule is enabled. There are some people who opt to use "they/theirs" pronouns for everybody, seemingly avoiding the issue. However, some trans people can feel invalidated by choosing to do this rather than using the pronouns they go by. I think it could be misleading or confusing to suggest that the use of these pronouns is insensitive, when instead a general guideline for pronouns could be more applicable.
Alternatives
Perhaps this particular rule could print a message reminding the user to "ensure that the pronouns they are using are appropriate for the person being addressed' or something to that effect. Possibly having it only occur 10% of the time would be good so that they don't get reminded every time they use those pronouns, and are instead occasionally reminded to ensure that they ask for/confirm and use the pronouns of the person they are addressing.
The text was updated successfully, but these errors were encountered: