-
Notifications
You must be signed in to change notification settings - Fork 13
fix: adjustments to german grammar #452
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
Open
toniarndt
wants to merge
1
commit into
main
Choose a base branch
from
356-grammar-check-german
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,103 @@ | ||
|
|
||
| # Styleguide Deutsch — Typografie & Sprache | ||
|
|
||
| ## Zweck | ||
| Ein praxisorientierter Leitfaden für einheitliche Texte: Bindestrich/Durchkopplung, Gedankenstrich/En-Dash, genderneutrale Formulierungen, Abstände (z. B. Währung), Listen‑Punktation und technische Hinweise für Mitarbeitende. | ||
|
|
||
| **Standard:** neutrale Partizipialformen (z. B. „Mitarbeitende") | ||
| **Optional:** Gender‑Doppelpunkt nach Accessibility‑Prüfung (z. B. „Mitarbeiter:innen") | ||
|
|
||
| ## Grundprinzipien | ||
| 1. **Lesbarkeit** vor stilistischer Spielerei | ||
| 2. **Konsistenz** über alle Publikationen hinweg | ||
| 3. **Barrierefreiheit** beachten (Screen‑Reader‑Kompatibilität prüfen) | ||
|
|
||
|
|
||
| ## 1. Bindestrich und Durchkopplung | ||
| **Regel:** Abkürzung + Wort = Bindestrich, kein Leerzeichen | ||
|
|
||
| **Beispiele:** | ||
| - `DB‑Mitarbeitende` | ||
| - `TGV‑Verbindung` | ||
| - `FIP‑Freifahrtschein` | ||
|
|
||
| **Hinweis:** Non‑breaking hyphen (U+2011) im CMS verwenden, um Zeilenumbruch zu vermeiden | ||
|
|
||
|
|
||
| ## 2. Striche — Bindestrich vs. Gedankenstrich | ||
|
|
||
| | Strich | Zeichen | Unicode | Verwendung | Beispiel | | ||
| |--------------- |---------|---------|-------------------|---------------------------------------| | ||
| | Bindestrich | `-` | U+002D | Zusammensetzungen | `E‑Mail`, `DB‑Mitarbeitende` | | ||
| | En‑Dash | `–` | U+2013 | Bereiche | `1999–2005`, `Hamburg–Berlin` | | ||
| | Gedankenstrich | `–` | U+2013 | Einschübe | „Das Projekt – Einschub – Text“ | | ||
|
|
||
| **Hinweis:** Em‑Dash (—) wird im Deutschen selten verwendet | ||
|
|
||
|
|
||
| ## 3. Geschlechtergerechte Sprache | ||
|
|
||
| **Standard (empfohlen):** Partizipialform (neutral) | ||
| - `Mitarbeitende`, `Studierende`, `Lehrende` | ||
|
|
||
| **Alternative (nur nach Prüfung):** Gender‑Doppelpunkt | ||
| - `Mitarbeiter:innen`, `Student:innen` | ||
|
|
||
| **Regeln:** | ||
| - Keine Mischung von Formen im selben Dokument | ||
| - Doppelpunkt besser für Screen‑Reader als Sternchen | ||
| - Entscheidung dokumentieren | ||
|
|
||
|
|
||
|
|
||
| ## 4. Abkürzungen und „z. B." | ||
| - „z. B." immer mit Punkten und **mit** folgendem Leerzeichen: `z. B. Beispiel` | ||
| - Bei Zeilenumbruch: geschütztes Leerzeichen verwenden: `z. B. Beispiel` | ||
|
|
||
|
|
||
| ## 5. Zahlen, Währung, Maßeinheiten | ||
| - Abstand zwischen Zahl und Einheit: `10 €`, `50 km` (geschütztes Leerzeichen U+00A0) | ||
| - Prozent: `10 %` (konsistent bleiben) | ||
| - Zahlenbereich: En‑Dash ohne Leerzeichen: `10–20`, `1999–2005` | ||
|
|
||
|
|
||
| ## 6. Listen / Aufzählungen | ||
| - Überschriften: kein Satzpunkt | ||
| - Stichwortlisten: keine Punkte am Ende | ||
| - Satzlisten: jedes Element mit Punkt abschließen | ||
| - Konsistenz: innerhalb einer Liste einheitliche Form | ||
|
|
||
|
|
||
| ## 7. Interpunktion / Leerzeichen | ||
| - Bindestriche: keine Leerzeichen vor/nach Bindestrich (`DB‑Mitarbeitende`) | ||
| - Gedankenstriche: in DE oft mit Leerzeichen („Text – Einschub – Text“) | ||
| - Konsistenzregel festhalten (z. B. Gedankenstrich mit/ohne Leerzeichen) | ||
|
|
||
|
|
||
| ## 8. Beispiele — vorher → nachher | ||
| | Vorher | Nachher | | ||
| |------------------|------------------------| | ||
| | DB Mitarbeiter | DB‑Mitarbeitende | | ||
| | TGV Verbindung | TGV‑Verbindung | | ||
| | 1999 - 2005 | 1999–2005 | | ||
| | 10€ | 10 € | | ||
| | z.B. | z. B. (mit NBSP: z. B. ) | | ||
|
|
||
|
|
||
| ## 9. Technische Hinweise | ||
| - Geschütztes Leerzeichen: U+00A0 — HTML: ` ` | ||
| - Non‑breaking hyphen: U+2011 — verhindert Zeilenumbruch am Bindestrich | ||
| - En‑Dash: U+2013 — für Bereiche und Verbindungen | ||
| - CMS: Vorlagen mit NBSP und non‑breaking hyphen vorgeben; Unicode‑Zeichen prüfen | ||
| - Barrierefreiheit: Screen‑Reader mit Genderzeichen testen; Dokumentation ergänzen | ||
|
|
||
|
|
||
| ## 10. Schnell‑Referenz | ||
| | Regel | Beispiel | | ||
| |----------------------|------------------------| | ||
| | Abkürzung + Wort | `DB‑Mitarbeitende` | | ||
| | Gender (neutral) | `Mitarbeitende` | | ||
| | Gender (Doppelpunkt) | `Mitarbeiter:innen` | | ||
| | Währung | `10 €` (NBSP) | | ||
| | „z. B." | `z. B. ` | | ||
| | Zahlenbereich | `10–20` | |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Grammatical error: 'kein' requires the nominative case, but 'Ermäßigung' is feminine, so it should be 'keine FIP Ermäßigung'. The same error occurs twice in this sentence.