Skip to content

i18n(de): rephrase gender notice in i18n-guide#13914

Open
trueberryless wants to merge 10 commits into
withastro:mainfrom
trueberryless:i18n/de-gender-notice
Open

i18n(de): rephrase gender notice in i18n-guide#13914
trueberryless wants to merge 10 commits into
withastro:mainfrom
trueberryless:i18n/de-gender-notice

Conversation

@trueberryless

@trueberryless trueberryless commented May 19, 2026

Copy link
Copy Markdown
Contributor

Description

The German translation of Astro docs only uses the male form for gendering because German gender rules make sentence structures often unreadable and would ruin the flow of documentation.

We therefore decided (back when we translated the tutorial I think) that we will add a gender notice somewhere, but haven't really discussed where to add it.

This PR updates the previous statement of our i18n guide1 to be a more profound gender statement, which translates to English as:

For the sake of readability, this documentation employs gender-neutral phrasing. Any personal titles or pronouns used are intended to include all genders, identities, and backgrounds equally. Our community thrives on diversity — we deeply value ensuring that everyone feels welcome, respected, and included here.

Footnotes

  1. The previous statement translated to English reads:

    We have decided against using gender-neutral language in our translations because it makes the texts harder to read, and there are currently no guidelines from Duden (official German dictionary) on the matter. We prefer to avoid gender-specific phrasing in our translations and word the texts in such a way that no one feels excluded.

@netlify

netlify Bot commented May 19, 2026

Copy link
Copy Markdown

Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit e74d01f
🔍 Latest deploy log https://app.netlify.com/projects/astro-docs-2/deploys/6a0cc5ac99123d0007792832
😎 Deploy Preview https://deploy-preview-13914--astro-docs-2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added the i18n Anything to do with internationalization & translation efforts - ask @YanThomas for help! label May 19, 2026
@astrobot-houston

astrobot-houston commented May 19, 2026

Copy link
Copy Markdown
Contributor

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
de/getting-started.mdx Localization changed, will be marked as complete. 🔄️
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@randomguy-2650

randomguy-2650 commented May 20, 2026

Copy link
Copy Markdown
Contributor

I have left a note on the original PR stating something about gendering as it is a slightly different case compared to the rabbit hole we went into during the big tutorial PR.


By the way, we could probably swap out some “generic masculine” terms for gender‐neutral ones, let me give you some examples to clarify what I mean:

  • Lehrer -> Lehrkraft
  • But not: Student -> Studierende (because nobody uses this, it sounds utterly weird)

@trueberryless

Copy link
Copy Markdown
Contributor Author

By the way, we could probably swap out some “generic masculine” terms for gender‐neutral ones, let me give you some examples to clarify what I mean:

* Lehrer -> Lehrkraft

* But not: Student -> Studierende (because nobody uses this, it sounds utterly weird)

Yes, but let's do that in another PR and not block this one 👍

@randomguy-2650 randomguy-2650 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eh… I’m not quite sure if it makes sense to merge this though because it deviates quite a bit from the original because of this language-specific note. Also, many sites that use the generic masculine don’t have a note at all.

So maybe more feedback from others if possible for this?

@github-actions

github-actions Bot commented Jun 23, 2026

Copy link
Copy Markdown

Preview deployment

✅ Deployment complete!

trueberryless and others added 4 commits June 23, 2026 20:19
…ditional content in this translation"

This reverts commit 747c9b8.
Co-authored-by: Chris Swithinbank <357379+delucis@users.noreply.github.com>
@trueberryless

Copy link
Copy Markdown
Contributor Author

Thanks to a wonderful suggestion by @delucis on Discord, I reverted all the previous changes and added the gender notice in our i18n-guide where a similar (but more "internal") note existed before. We can use that ideally as a perfect place for this statement 👍

I think this is a better solution, wdyt @randomguy-2650?

@trueberryless trueberryless changed the title i18n(de): add German gender note to index page i18n(de): rephrase gender notice in i18n-guide Jun 23, 2026
Comment thread i18n-guides/deutsch.md Outdated
- Wir übersetzen alle Kommentare in Code-Beispielen.
- Komponenten-, Klassen- und Variablennamen in Code-Beispielen werden nicht übersetzt.
- Wir haben uns gegen das Gendern in unserer Übersetzung entschieden, weil es die Lesbarkeit der Texte verschlechtert und noch keine Duden-Vorgaben dafür existieren. Wir vermeiden lieber geschlechtsspezifische Formulierungen in unseren Übersetzungen und formulieren die Texte so, dass niemand sich ausgeschlossen fühlen muss.
- Aus Gründen der besseren Lesbarkeit wird in dieser Dokumentation auf die gleichzeitige Verwendung mehrgeschlechtlicher Sprachformen verzichtet. Sämtliche Personenbezeichnungen gelten als geschlechtsneutral und beziehen sich gleichermaßen auf alle Geschlechter. Unsere Gemeinschaft lebt von Vielfalt – wir legen großen Wert darauf, dass sich jede Person, unabhängig von der Identität, hier willkommen und angesprochen fühlt.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if it would be good to still preserve the intent of this sentence in there somewhere:

Wir vermeiden lieber geschlechtsspezifische Formulierungen in unseren Übersetzungen und formulieren die Texte so, dass niemand sich ausgeschlossen fühlen muss.

For example, something like

Womöglich vermeiden wir geschlechtsspezifische Formulierungen in unseren Übersetzungen und formulieren die Texte so, dass niemand sich ausgeschlossen fühlen muss. Wo solche Formulierungen nicht möglich sind, wird auf die gleichzeitige Verwendung mehrgeschlechtlicher Sprachformen verzichtet aus Gründen der besseren Lesbarkeit. etc…

Just to underline that the aim is still to use neutral language as much as possible but acknowledge it’s not always possible.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the phrasing in 08f541f (this PR). Wdyt?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

i18n Anything to do with internationalization & translation efforts - ask @YanThomas for help!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants