German translation: status and integration question
Hi @sumn2u,
Not sure if it was just overlooked, but a quick βthanksβ wouldβve been nice β Iβve translated over 1000 lines into German and reported several bugs.
Before continuing with the remaining files, Iβd like to know when German will be officially added. Itβs not in LANGS.md, and most other languages are incomplete. Even English has some inconsistencies.
Without proper integration, any new language will face the same issues β no structure, no testing, no clear path.
Looking forward to your reply, @mmunin
Thank you for raising this question and for your contribution. Weβll begin rolling out the merged chapters for German translation starting next week.
In this project, English is used as the source of truth, so there may be cases where some topics haven't been translated yet. As new topics and chapters are added, the translations may require updates or fall out of sync.
To help with this, we have a GitHub workflow that monitors changes in the English folder and automatically creates translation issues whenever updates are detected.
Hi @mmunin, I've merged the German translation; readers can now access the translated chapters thanks to your contribution! We'll be releasing the PDF version once the remaining content has been translated.
Hi @sumn2u, thanks for merging β great to see the German translation live! How about a tracker issue? I could set it up like this:
Translation Progress Overview
Total files in English: 183
Remaining files per language
| Language | Remaining Files |
|---|---|
| π©πͺ German (de) | 137 |
| π³π΅ Nepali (np) | 92 |
...
Just an idea β I could add it here in the comment,
or set up a separate tracker issue that contributors can help update.
Whatever works best for you!
Hi @sumn2u, thanks for merging β great to see the German translation live! How about a tracker issue? I could set it up like this:
Translation Progress Overview
Total files in English: 183
Remaining files per language
Language Remaining Files π©πͺ German (de) 137 π³π΅ Nepali (np) 92 ... Just an idea β I could add it here in the comment, or set up a separate tracker issue that contributors can help update. Whatever works best for you!
Wow, this is helpful. I think it would make more sense to create a separate issue and use that as a base.
Hey @sumn2u, check out #302 - Maybe we can link the existing translations issues or set them up as sub-tasks.
Hey @sumn2u, check out #302 - Maybe we can link the existing translations issues or set them up as sub-tasks.
I think the sub-task makes more sense.
I initially thought using subtasks would be ideal. But with more than 10 subtasks, it quickly becomes hard to manage β and we can't link them individually. Iβll give it some more thought β how are you thinking of linking it?
I initially thought using subtasks would be ideal. But with more than 10 subtasks, it quickly becomes hard to manage β and we can't link them individually. Iβll give it some more thought β how are you thinking of linking it?
I think we can split the translation into:
-
Part 1: Core Basics includes the Preface, Introduction, and foundational chapters such as Basics, Numbers, Strings, Conditional Logic, Arrays, Loops, Functions, Objects, Date and Time, JSON, Error Handling, and related exercises.
-
Part 2: Extended Topics covers intermediate and applied concepts including Modules, Regular Expression, Classes, Browser Object Model (BOM), Events, Promise/async-await, Miscellaneous topics, and Server Side content.
-
Part 3: Bonus Sections contains advanced and supplementary material like Interview Questions, Design Patterns, File System, ES6 Concepts, Animation Resources, Complexity, JavaScript Behind the Scenes, and Document Object Model (DOM).
-
Part 4: Wrap-up wraps up with References, Resources, and Credits.
This prioritizes the core essentials first for translation, while allowing bonus and advanced chapters to be done later or in parallel, maintaining consistency and manageable workloads.
Let me know what you think?
Hi, I've been thinking a bit about the project β especially about structure and how we could make progress more visible. Splitting the book into modular sections seems like a good idea. After that, translations could be merged more systematically. That might also help attract new translators or re-engage previous contributors.
Right now, it's hard to tell how far along the book is in each language. My suggestion would be:
a separate tracker issue for each language, link them to the main issue Tracker
Later, Use a GitHub Action to update progress automatically, visualize everything in the project board
How do you envision the workflow? At what stage would merging translations make sense β and when would generating a PDF be appropriate? I might be able to show you the structure I had in mind later this evening.
The ideal case for releasing a PDF would be once all the text has been fully translated. However, there are situations where the translation is complete but out of sync because new content has been added to the English (main) version. Let me know what you were thinking.
here the structures:
Original Language: English (en) Total Files: 183
Translation Tracker β German (de)
Progress by Language
| Language | Missing Files | Progress | Language Issue | Board |
|---|---|---|---|---|
| Spanish (es) | 30 | β 84% | Issue 101 | Board |
| Indonesian (id) | 63 | π‘ 66% | Issue 102 | Board |
| French (fr) | 81 | π‘ 56% | Issue 103 | Board |
*Maybe leave out the board for now, but it could look like this.
This structure for each language: Translation Tracker β π©πͺ German (de)
Status: 137 out of 183 files missing
Progress
| Section | Total Files | Remaining to Translate |
|---|---|---|
| Part 1 β Core Basics | 50 | 35 |
| Part 2 β Extended Topics | 60 | 45 |
| Part 3 β Bonus Sections | 50 | 40 |
| Part 4 β Wrap-up | 23 | 17 |
*List existing issues as subtasks underneath. Numbers are illustrative, Possibly notes on how to contribute, some information, and appropriate labels for it. What do you think?
Nice work. It's clear now. BTW, how did you count the files that are missing translation, is there a script for it?
Itβs still doable manually for now β Iβm using Total Commander like in the good old days. Havenβt written a script for it yet.
I can try it out, but because of the exam it won't be until next week
I can try it out, but because of the exam it won't be until next week
Thanks. I think we can skip the automation part for now and revisit this once the translation is complete.