Skip to content

Adopt Gender-Neutral Language in German Translations #197

@Ralf-Brauchler

Description

@Ralf-Brauchler

Goal:
As a user, I want the German translations within the c4 application to use gender-neutral and inclusive language to ensure a welcoming and accessible user experience for everyone.

Description:
The current German translations in the application contain terms that are not gender-neutral. Using inclusive language is a standard practice in modern software development and aligns with the principles of diversity and inclusivity that are important for an open-source community.

This ticket aims to identify and update non-gender-neutral terms in the German localization files with appropriate inclusive alternatives.

Examples of terms to review and update:

  • Benutzer -> z.B. Nutzer:in, Person, Konto
  • Benutzergruppe -> z.B. Nutzergruppe, Gruppe
  • Benutzername -> z.B. Nutzername
  • Chat-Benutzer -> z.B. Chat-Nutzer:in, Chat-Teilnehmer:in
  • Assistent -> remains unchanged (Assistent)

Tasks:

  1. Audit German Translation Files: Review all German language files (.po, .json, or whatever format is used) to identify terms that are not gender-neutral.
  2. Identify Inclusive Alternatives: Determine appropriate gender-neutral alternatives for the identified terms. LLMs can be a helpful tool in suggesting alternatives for various contexts.
  3. Update Translation Files: Replace the non-gender-neutral terms with the agreed-upon alternatives in the translation files.
  4. Review Contexts: Ensure the chosen alternatives fit correctly within the grammatical and contextual flow of the user interface.
  5. Test Changes: Verify that the updated translations display correctly in the application and that the language is consistently inclusive.

Motivation:
Adopting gender-neutral language in translations is a step towards creating a more inclusive product that respects users of all genders and aligns with broader efforts towards accessible and equitable communication. This is a standard best practice in many software projects today.

Metadata

Metadata

Assignees

Labels

No fields configured for Feature.

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions