Skip to content

Use the generic masculine in the German UI strings - #331

Open
happyarts wants to merge 1 commit into
kaixxx:mainfrom
happyarts:fix/german-gendered-labels
Open

Use the generic masculine in the German UI strings#331
happyarts wants to merge 1 commit into
kaixxx:mainfrom
happyarts:fix/german-gendered-labels

Conversation

@happyarts

Copy link
Copy Markdown

Split out of #324 so the technical header change there is not tied to a
language decision — this one is entirely yours to accept or drop.

The German locale was the only one using gender-inclusive forms, and only in
five of the strings that talk about speakers:

  • label_speaker: Sprecher:in erkennen:Sprecher erkennen:
  • speaker_identification: Sprecher:innenidentifikationSprecheridentifikation
  • start_identifying_speakers: Sprecher:innen identifizieren...Sprecher identifizieren...
  • err_identifying_speakers: ... Erkennung der Sprecher:innen.... Erkennung der Sprecher.
  • err_user_cancelation: Abbruch durch Nutzer:inAbbruch durch Nutzer

The rest of the file already used the generic form (e.g. job_tt_canceled:
"Auftrag vom Benutzer abgebrochen"), so the UI read inconsistently. This unifies
on the generic form; trans/noScribe.de.yml is the only file touched.

🤖 Generated with Claude Code

The German locale was the only one using gender-inclusive forms
("Sprecher:innen", "Nutzer:in"), and only in five of the strings that talk
about speakers -- the rest of the file already used the generic form, so the
UI read inconsistently. Unify on the generic form.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant