Skip to content
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

Missing gender sensitive language #1844

Closed
osmers opened this issue Nov 9, 2022 · 1 comment · Fixed by #1852
Closed

Missing gender sensitive language #1844

osmers opened this issue Nov 9, 2022 · 1 comment · Fixed by #1852
Assignees
Labels
🐛 bug Something isn't working ❗ prio: medium Should be scheduled in the forseeable future. ☺️ effort: low Should be doable in <4h
Milestone

Comments

@osmers
Copy link

osmers commented Nov 9, 2022

Describe the Bug

Gender sensitive language for some cases is missing

Steps to Reproduce

  1. Go to Benutzer:innen
  2. Click to create a new account
  3. See that the user name is still called Benutzername
  4. See that the description for active status is as follows.
    Legt fest, ob dieser Benutzer aktiv ist. Kann deaktiviert werden, anstatt Benutzer zu löschen.

Expected Behavior

All words should be gendered or gender neutral

Actual Behavior

The male word Benutzer is used

Additional Information/suggestion

Rename single word Benutzer to Benutzer:in or Benutzer:innen depending on context. If it is a composite word, like Benutzername, use Kontoname
Possible need to change the english original accordingly from user name to account name

@osmers osmers added 🐛 bug Something isn't working ❗ prio: medium Should be scheduled in the forseeable future. ☺️ effort: low Should be doable in <4h labels Nov 9, 2022
@osmers osmers added this to the Backlog milestone Nov 9, 2022
@JoeyStk JoeyStk self-assigned this Nov 9, 2022
@JoeyStk JoeyStk added the 👼 help wanted Extra attention is needed label Nov 9, 2022
@JoeyStk
Copy link
Contributor

JoeyStk commented Nov 9, 2022

This is not as straightforward as it might seem on first glance. This issue is due to the django base user form. It has nothing to do with our translation (file). There is a way to change this, but the Django documentation warns to do so. I think we have to reconsider, if we really want to do this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working ❗ prio: medium Should be scheduled in the forseeable future. ☺️ effort: low Should be doable in <4h
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants