-
Notifications
You must be signed in to change notification settings - Fork 48
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
Translation in multiple languages #132
Comments
@acehreli would you be willing to translate it to Turkish? (once it's moderately stable) |
Of course! :) Ali On 05/25/2016 09:28 AM, Sebastian Wilzbach wrote:
|
Thanks all translators for their help! Lets make that happen when the storm of pull requests and changes has passed :-) |
Willing to! But @DlangRen is translating "Prg in D" into Chinese at present. As the only active dlang community in China, we are extermly short of volunteers. So we want to finish this project first due to the lack of helping hands. We still waiting for an upturn of dlang in China. Anyway we will start translating this as soon as the current one is completed. |
@meatatt, Chinese community may be slow in growth but rest assured, perhaps due to large population, ddili.org gets almost equal visitors from China and US. (There has been months where Chinese visitors were more than US visitors.) This month so far: US China The next country in line is Turkey with about 25% of those numbers. Ali |
@acehreli Wow! This is truly beyond our imagination. Thank you :) |
Just a quick update from the dev team, with #276 the last real blocking PR for multi-lingual just went in. Also we now have separated each chapter into a single file, s.t. translation will be easier and we now feature an edit button on the tour that directly takes one to the corresponding markdown file. @stonemaster and I will work on getting basic macro support (#55) to avoid putting redundant HTML into the markdown. Meanwhile we encourage everyone to read through the tour and find nitpicks. I guess after another heavy round of reviewing and nitpicking, the fight for the first translation may begin ;-) |
guys, for sure I can translate in Romanian, and also my colleague, Louis will do it in French. just ping us :) |
@claudiug Awesome! Give us a couple weeks for polishing and then we'll be ready for the translation marathon :-) |
Hi guys, |
@lodo1995 Not yet! Awesome, thanks we'll come back to you! |
For sure I'm in @stonemaster !! |
Hey all, a lot of time has passed by and @stonemaster and I feel that the tour has matured enough to be ready for the translation into multiple languages. @dmi7ry has already done a huge step forward for the Russian translation and I started myself with the German one. Hence I would look to share my experience of translating the tour to German with you and I prepared a small guide for translators: https://github.com/stonemaster/dlang-tour/wiki/Tips-for-translators And I have also written a small, optional tool that automates submitting multiple PRs: https://github.com/wilzbach/splitup-prs (It's not perfect, but it already saves time for me) Some key points
Let's get the party started 🎉 and let the race begin! |
Hey all, just a quick update from my side. We have seen such a massive increase in PRs for the translations that we split them up into submodules (#454). In case you didn't follow this closely: the organization dlang-tour has been founded and contains a repo for each language which will be embed into the main tour & some languages have already been linked: http://tour.dlang.io/tour/sv/welcome/welcome-to-d (they are still WIP and thus not linked from the main repo) From the process above nearly nothing should have changed except for two things:
For my readers from the future: if you want to start a translation of a new language or join an existing team, just ping me or @stonemaster, we are happy to help. Last but not least don't hesitate to ask questions if you run into troubles and don't forgot to make a PR for every file (see above for more tips). |
I am closing this issue now as the translations are on a good way and in same cases already finished :) |
We should probably set a milestone once it's stable enough, s.t. we can start translating in multiple languages. So I keep this here open for people to volunteer for their language and notification once we want to start going multi-lingual:
@buggins offered to translate into Russian
@wilzbach offered to translate to German
It probably makes sense then to put the translated commit as plain text comment in the regarding language, s.t. it's easy to update the languages once in a while.
The text was updated successfully, but these errors were encountered: