Skip to content
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

[de] German Translation Guide #132

Merged
merged 3 commits into from
Apr 20, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 46 additions & 0 deletions chapters/de/TRANSLATING.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
1. We use the informal "you" (i.e. "Du" instead of "Sie") to keep the tone jovial.
Copy link
Member

Choose a reason for hiding this comment

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

This is a great description!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you!

However, don't use slang or local language, so use the correct form of "als",
and "wie" rather than the locally accepted form.

2. Don't translate industry-accepted acronyms. e.g. TPU or GPU.

3. The German language accepts English words especially in modern contexts more than
many other languages (i.e. Anglicisms). Check for the correct usage of terms in
computer science and commonly used terms in other publications.

4. Beware of "false friends" in German and English translations. Translators are trained
for years to specifically avoid false English friends and avoid anglicised translations.
e.g. "Daten" is "data", but "dates" is "Termine". For more examples refer to:
https://lal.de/blog/false-friends-falsche-freunde/

5. Keep voice active and consistent. Don't overdo it but try to avoid a passive voice.

6. Refer and contribute to the glossary frequently to stay on top of the latest
choices we make. This minimizes the amount of editing that is required.

7. Keep POV consistent.

8. Smaller sentences are better sentences. Apply with nuance.

9. If translating a technical word, keep the choice of German translation consistent.
This does not apply for non-technical choices, as in those cases variety actually
helps keep the text engaging.

10. This is merely a translation. Don't add any technical/contextual information
not present in the original text. Also don't leave stuff out. The creative
choices in composing this information were the original authors' to make.
Our creative choices are in doing a quality translation.

11. Be exact when choosing equivalents for technical words. Package is package.
Library is library. Don't mix and match.

12. Library names are kept in the original forms, e.g. "🤗 Datasets", however,
the word dataset in a sentence gets a translation to "Datensatz".

13. As a style choice prefer the imperative over constructions with auxiliary words
to avoid unnecessary verbosity and addressing of the reader, which seems
unnatural in German. e.g. "Siehe Kapitel X" - "See chapter X" instead of
"Dies kannst du in Kapitel X sehen" - "You can see this in chapter X".

14. Be careful with sentences using "wir", which can seem unnatural at best and
condescending at worst in German.
5 changes: 5 additions & 0 deletions chapters/de/_toctree.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,8 @@
sections:
- local: chapter0/1
title: Einführung

- title: Wörterverzeichnis
sections:
- local: glossary/1
title: Wörterverzeichnis
87 changes: 87 additions & 0 deletions chapters/de/glossary/1.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,87 @@
# Wörterverzeichnis

| Original | Übersetzung |
|-----------------------------|---------------------------------|
| Abstraction | Abstraktion |
| Backward Pass | Rückwärtsalgorithmus berechnen |
| Batch | Batch |
| Chapter | Kapitel |
| Class | Klasse |
| Code | Code |
| Colab Notebook | Colab Notebook |
| Command | Befehl |
| Configuration | Konfiguration |
| Course | Kurs |
| Dependency | Abhängigkeitsbeziehung |
| Deployment | Deployment |
| Development | Entwicklung |
| Distribution | Verteilung |
| Download | Download |
| Feature | Feature |
| Folder | Ordner |
| Forward Pass | Vorwärtsalgorithmus berechnen |
| Function | Funktion |
| Google | Google |
| Hugging Face | Hugging Face |
| Incompatibility | Inkompatibilität |
| Inference | Inferenz |
| Library | Bibliothek |
| Linux | Linux |
| Load | laden |
| macOS | macOS |
| Model | Modell |
| Model Hub | Model Hub |
| Module | Modul |
| Natural Language Processing | Computerlinguistik |
| Package | Paket |
| Package Manager | Paektverwaltung |
| Parameter | Parameter |
| Python | Python |
| Pytorch | Pytorch |
| Save | speichern |
| Script | Script |
| Self-Contained | in sich abgeschlossen |
| Setup | Installation |
| TensorFlow | Tensorflow |
| Terminal | Terminal |
| Tokenizer | Tokenizer |
| Train | Training |
| Transformer | Transformer |
| Virtual Environment | Virtuelle Umgebung |
| Windows | Windows |
| Working Environment | Arbeitsumgebung |
| Workload | Auslastung |
| Workspace | Workspace |


## Abkürzungen

| Original | Übersetzung |
|-----------|-------------|
| NLP | CL |
| API | API |
| GPU | GPU |
| TPU | TPU |
| ML | ML |

## Notes

Please refer to [TRANSLATING.txt](/chapters/de/TRANSLATING.txt) for a translation guide. Here are some excerpts relevant to the glossary:

- Refer and contribute to the glossary frequently to stay on top of the latest
choices we make. This minimizes the amount of editing that is required.
Add new terms alphabetically sorted.

- The German language accepts English words especially in modern contexts more
than many other languages (i.e. Anglicisms). Check for the correct usage of
terms in computer science and commonly used terms in other publications.

- Don't translate industry-accepted acronyms. e.g. TPU or GPU.

- If translating a technical word, keep the choice of German translation consistent.
This does not apply for non-technical choices, as in those cases variety actually
helps keep the text engaging.

- Be exact when choosing equivalents for technical words. Package is package.
Library is library. Don't mix and match.