-
Notifications
You must be signed in to change notification settings - Fork 631
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
Guidelines for translating the Turing Way into other languages #767
Comments
Would be happy to help with Chinese translation 😊 |
Awesome @tonyyzy! That would be so great! I need to have a chat with @choldgraf and maybe @emdupre about structing having translated versions of the book but once we've got the location figured out then it would be amazing to have translated pages! Is there a page you'd like to start with? |
Hi @KirstieJane! Yes, I guess structuring different language versions efficiently is very important. It would be nice to have a system notifying us when the English version's paragraph has changed then ask us to review/modify the translated version. Or even some plugins that map the original paragraph to the translated paragraph to reduce duplication of files...just some ideas. I have never done any formal translation work so I think some guidelines regard wording in addition to the contributing guidelines would be really helpful! I will start with Introduction and Reproducibility chapters. Can't make any promise of progress but holiday season should give me more time to work on this 😀 |
I know that Jupyter has used Transifex for this before: https://www.transifex.com/ maybe that's worth looking into? I'm not sure how it works though... For Jupyter Book and translations, you could either have top-level folders in your content folder that correspond to languages (e.g. |
Just saw that Electron uses Crowdin as their internationalisation solution https://crowdin.com/. Looks very similar to Transifex. Although they both seem to offer free open-source plan, don't know how open-source friendly they are. |
The transifex and the crowdin all look fine, I will be very glad to translate some chapters of the Turing Way into Chinese when you decide one. |
Some notes from collaboration cafe 18/12/2019 with @KirstieJane:
|
Hello @tonyyzy , it is amazing that you have listed many solutions that enable us to translate the Turing Way. @minnieho1115 and I are trying to translate this book and have initially finished four chapters as a start (please see: https://github.com/sparkler0323/The-Turing-Way-Chinese-translation). Maybe we could determine a platform that we can keep working on it? |
Hi @sparkler0323 - could you add a little explanation about why you're working in a new repository rather than a fork of the Turing Way? And why you've chosen a word document rather than markdown? |
新年好 @sparkler0323 @minnieho1115! Apologise for slacking 😛 I'm leaning towards the PO-file solution like the carpentries one (open source for the win!). A quick search shows that VSCode has plugins for PO file though I haven't tried them out (https://marketplace.visualstudio.com/items?itemName=mrorz.language-gettext) I'll have a play with the automation toolchains and report back by next week (feel free to have a try as well!) My goal is to set up the basics before the book dash then mostly do the translation work during the book dash. |
Hi @KirstieJane , this is a temporary repository and it's a good idea to folk the Turing Way. Yini and I are collaborating using word and we will be very glad to transform the work version into the Markdown once we have established the platform with @tonyyzy . |
新年好,很高兴认识你 @tonyyzy Sounds a really nice solution! I'm not familiar with the VSCode but I will be happy to learn your pipeline next week 😄. I think it's very exciting to use automation toolchains instead of our current manual translation. Once setting up the basics, we are also looking forward to knowing your suggestions on the translation style we have finished. |
Hi @KirstieJane @tonyyzy , I have deleted the previous repository and provisionally store a Markdown version in the following place: https://github.com/sparkler0323/the-turing-way/blob/master/book/Translation/Chinese_Chapter1_4.md. @minnieho1115 and I will transform the word version into the Markdown version later. |
@tonyyzy 😃春节快乐!Thank you very much for your suggestions. Look forward to learning your pipeline next week. It would be suuuuper great to have automated tools. |
This comment has been minimized.
This comment has been minimized.
Hi everyone, Super glad to see so many interests in this part of the project. I wanted to share The Carpentries English-Spanish translation GitHub repo, in case you haven't looked at it yet. A group of people worked on it remotely by using a project management feature of the GitHub and maintaining a progress table. Rayna Harris has explained this process in her poster in this tweet thread In their first-round, they did the following:
For the French translation, a different group used another process which I have requested the repo and more info. Another example for the translated materials I really admire is by the A Byte of Python project that has been translated in many many languages and exists on GitHub. I did not find their how-to guide very helpful, but maybe their process exists in details somewhere. Here is a translation in chinese: https://bop.mol.uno/. |
Hi @malvikasharan, super pumped to have you here! Thanks for sharing these, the guidelines will be very useful to get us started! I guess the difference between our book and most of the other projects I've seen is our content is evolving much faster. So I think it should be a conscious decision to keep the translations in the same repo as the English version. I've figured out most of the kinks in my fork https://github.com/tonyyzy/the-turing-way
|
@tonyyzy this is amazing. We should think of a way to record the process and quirks that you have mentioned and will appear on the way of setting this infrastructure. Maybe a standard change log or a document within your forked repo (or may be even the main repo) for process development update. Where do you think I and others can help you with at this point? Yini and Ang will be in the best position to help develop the glossaries that are very Turing Way specific (for consistency and translation purposes) and can add to the process development update from the translation side. |
Hello! @crangelsmith and I would be interested to help with the Spanish translation. We will start looking at the documentation and guidelines already shared in this issue. Let us know if you have recommendations about what to prioritize and where to start! |
@camachoreina That would be awesome! What kind of support can we provide you to get started? |
@malvikasharan for sure, I will write documentation and a quick starter. @camachoreina @crangelsmith awesome to have you on board, I will share the Transifex link with you once it's setup then you can join as collaborators. |
@tonyyzy Can you please walk me through the process of integration in one of the coming days over a call? I don't really know the Transifex integration and can use your help to understand this system better. |
Edit: Just saw the message on Gitter, will wait for organisation admin to approve then @malvikasharan definitely, we can talk over it during the book dash? It's very new to me as well and I'm still figuring it out. I requested the Transifex integration to be installed on this repo, could you approve the request please? |
@camachoreina @crangelsmith @sparkler0323 @minnieho1115 Here we go! Please go to here then click "Help Translate". You can login with your desired account or register a new one. Then it will show you the project overview and you can select a language and start translating! Let me know if anything is unclear. I'm new to the interface too. Please restrain from reviewing your own changes – if you click "Save Changes" then let others do the reviewing and click "Review". @KirstieJane @malvikasharan I've invited you two as I have your emails. |
@tonyyzy thank you sooo much for moving ahead with this. Learning so much from this process and your work already. 🙌 |
@tonyyzy Looks great now! I just send a request to join the Chinese translation group. Looking forward to using this! |
@malvikasharan here's the quick starter guide. I'll add the implementation details when I have a bit more time :) |
You are a super start @tonyyzy <3 so excited to add this development in the report. |
Sorry I've not been able to get to this notification till now. I'm glad you are using Well done @tonyyzy for that guide! Feel free to ask me anything. I'm keeping all the info across different repositories in https://github.com/carpentries-i18n . I'm planning to document it all better and have a translations handbook. |
@dpshelio Thanks! Your carpentries i18n stuff was very helpful to get us started. Transifex works so far so good, we will test its PR function very soon. Kirstie talked about turning the translation guide into a book chapter for the Turing way once it's more comprehensive. I'm happy to contribute to your handbook too! |
Hi @camachoreina and @crangelsmith, I could help out in the Spanish translation :-). |
Hi @psubias , thanks this is great. Please join the Spanish team in Transifex https://www.transifex.com/theturingway/theturingway/dashboard/, and maybe we can have a catch up at some point soon?. We are starting with the translation of the first this week. |
Happy to say that this is being introduced in #3153 🎉 |
Summary
I'm chatting with @minnieho1115 & @sparkler0323 about translating some of the content in the Turing Way in to Chinese. It makes sense for us to capture a few guidelines about what that would look like!
What needs to be done?
Who can help?
Updates
No updates so far
The text was updated successfully, but these errors were encountered: