Adopt gender-neutral language in German translations (user-related terms)

[Copilot]

Updated German translations to use inclusive, gender-neutral language for user-related terminology, replacing gendered terms with modern German alternatives.

Changes

Translation Updates

Core user terminology:

• Benutzer → Nutzende (general) / Person (individual accounts)
• Benutzername → Nutzername
• Benutzergruppe(n) → Nutzergruppe(n)
• Chat-Benutzer → Chat-Nutzer:in (colon-inclusive form)

Assistant references:

• Assistent(en) → Remains unchanged (kept as Assistent(en))

Files Modified

• frontend/src/texts/languages/de.ts - 23 translation strings
• backend/src/localization/i18n/de/texts.json - 4 translation strings

Example

// Before
common: {
  chatUser: 'Chat-Benutzer',
  userGroup: 'Benutzergruppe',
}
extensions: {
  configurations: 'Assistenten',
  createConfiguration: 'Assistent erstellen',
}

// After
common: {
  chatUser: 'Chat-Nutzer:in',
  userGroup: 'Nutzergruppe',
}
extensions: {
  configurations: 'Assistenten',  // Unchanged
  createConfiguration: 'Assistent erstellen',  // Unchanged
}

Note

• Pre-existing typo in key errorLastConfigurationdDeleted (missing 'e') left unchanged as it's used consistently across the codebase and unrelated to this change.
• The term "Assistent" and its variants remain unchanged per maintainer preference, keeping the scope focused on user-related terminology only.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Adopt Gender-Neutral Language in German Translations</issue_title>
<issue_description>
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 -> z.B. Assistenz, Helfer

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.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Adopt Gender-Neutral Language in German Translations #197

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[andres-cq]

@copilot Assistent -> remains unchanged (Assistent)

[Copilot]

@copilot Assistent -> remains unchanged (Assistent)

Updated in commit b64de6e. "Assistent" and its variants now remain unchanged. Only user-related terms (Benutzer → Nutzende/Person, Benutzergruppe → Nutzergruppe, etc.) have been updated to gender-neutral forms.

[surt91]

I do not think that "Person" is the correct word here. "Person löschen" sounds even threatening.