Multilingual support with Crowdin

[InessaPawson]

For the up-to-date information on this issue refer to the following:
 https://github.com/Shekharrajak/scipy-sphinx-theme-v2/issues

Testing with the current NumPy doc: numpy/numpy#14648

The latest Sphinx theme: Demo link

[Shekharrajak]

Refer: #61, #62

[rgommers]

Just did some testing, this looks nice! I think for testing we can do Mandarin (@zjpoh offered to help) or Hindi if you want to do that @Shekharrajak. I think Dutch was good to try the interface, but we don't really need/want a Dutch translation - Dutch people are perfectly happy with English usually.

[Shekharrajak]

Yeah! I will try to do that.

[rgommers]

Related gh-329 for Korean translation.

[rgommers]

I think we're good to go on this, the content is stable and everything seems to work. I'll re-enable the language selector as well.

@zjpoh would you still be interested to work on the Chinese translation?

I've added a wiki page at https://github.com/numpy/numpy/wiki/Translations-of-the-NumPy-website on how to get started.

[rgommers]

Re-enabling the dropdown is a matter of undoing the small patch in gh-171

[rubentl134]

I would like to participate on the Spanish translation. Is there any way I can start? I feel kind of lost here. Sorry

[rgommers]

That's great, thanks @rubentl134! Spanish is already enabled on Crowdin, so to get started see the instructions at https://github.com/numpy/numpy/wiki/Translations-of-the-NumPy-website. Basically, sign up for Crowdin via the link there, select Spanish, and start:)

If you have any issues, please let us know.

[rgommers]

Can you use Weblate instead, so I can contribute without getting spied on, leak info, and also contribute to their closed translation memory?

We have spent significant time setting up Crowdin, after good experiences Spyder had with it. And the Crowdin team has been quite helpful, so I see no reason to switch.

You need a license to be able to use the translations btw. :)

I don't know what you mean by that.

[rgommers]

@comradekingu we noticed you're going around and posting the same request on many projects in this scientific Python ecosystem:

sympy/sympy.github.com#130 (comment)
jupyterlab/jupyterlab#8829 (comment)
carpentries/glosario#59

Furthermore, you're one of the top contributors to Weblate, and clearly only interested in promoting your own tool with no intention to actually contribute to NumPy or any of the other projects linked above. That's just rude behaviour, please stop doing that. If you want to promote Weblate, please do so on your own project/website/blog/channels.

[rgommers]

Please stop posting here. You are being rude. At this point I have zero interest in interacting with you more.

[giacomodeodato]

I would like to contribute, are you planning to translate in Italian as well?

[rgommers]

Hi @giacomodeodato, thanks for asking. We aimed to start with the languages for which we expect there's most demand (Chinese, Spanish, Portuguese, Japanese, Korean), and expand based on that experience. I'm not sure, but I would personally expect that most Italians who use NumPy would be okay using English, so it'd be lower prio. It's always hard to say no to an offer of help, but would you mind if we didn't do Italian at least till we get a better sense of how maintainable adding more languages is?

[giacomodeodato]

Of course, I totally understand

[rgommers]

@goanpeca suggested that we should organize a sprint to push translations forward. That does seem like a good idea. The rest of this year is already very full, but maybe we can pick a date in January - I'll put it on the community meeting calendar to discuss.

[MahatKC]

I'd be happy to help with Portuguese translation.

[rgommers]

Thanks @MahatKC! The Portuguese translation is actually pretty far along, thanks to @melissawm. With another push we should be able to get it complete and published relatively soon. Please jump in! Instructions are at https://github.com/numpy/numpy/wiki/Translations-of-the-NumPy-website, let us know if you need any help.

[melissawm]

@MahatKC let me know if you need any help - I'm in the process of populating the glossary so we can get consistent translations. Thanks!

[melissawm]

@MahatKC are you available to review the Portuguese translation?

[vinisalazar]

Hi, I'd also like to help with the review. I considered starting by reviewing the case-studies directory. Would that work @melissawm ?

[melissawm]

Sure, pick whatever document you prefer!

[steppi]

No worries @AtsushiSakai, it's a reasonable number of inquiries actually, and it's part of my job now to support the translation effort. It's because news.md got updated, and Crowdin seems to be a little dumb about what's changed in the file, and may just revert things even if they should still be translated correctly. If you go through news.md again on Crowdin, your old translation will be the top suggestion for each fragment if it still matches. I spent a lot of time trying to figure out a better way to bring back the old translations, but using the suggestions in Crowdin is unfortunately the best I've found so far.

If Crowdin can suggest the old translations, it must be able to bring them back automatically, so I'll ask support about this.

[AtsushiSakai]

@steppi Hi. It seems that the translation of NumPy was recently migrated from regular Crowdin to Crowdin Enterprise. However, translation request emails are coming from both projects. Is it correct to understand that translations should be done in the Enterprise project?

[steppi]

@AtsushiSakai. I think it would be fine right now to use either, since I don't directly merge the PRs Crowdin generates, but just do the equivalent of cherry picking commits from them, so use whichever has the most complete translations right now. Later on I can use the Crowdin CLI to get the most up to date translations into the enterprise account if needed. In a couple weeks, I plan to get all of the latest translations into the enterprise account, announce to translators across a couple channels that we're transferring, and then see if I can archive the original account.

[SaeedForoutan]

I would like to contribute to Persian translation. But, I couldn't find the Persian language option on Crowdin. Is there a specific request or procedure for adding this language?

[steppi]

Hi everyone. In January I started the process to migrate numpy.org to the Scientific Python Crowdin enterprise organization. However, this process wasn't completed, and all translations have still been carried out in the original NumPy Crowdin account. Today I'm going to complete this process and archive the numpy.org project in the NumPy Crowdin account. Going forward, all translations will be done in the Scientific Python enterprise organization. I hope the disruption will be minimal.

@SaeedForoutan, sorry for the long delay in responding. That's great that you want to help out. After I complete the migration described above, I can add Persian as a language to the project and reach out to you again about getting you invited to the Scientific Python Crowdin enterprise org.

[AtsushiSakai]

@steppi
Thank you for the migration work.

Can I ask a question about the Japanese translations in Croudwin? Currently, there are three top directories in the Japanese translation directory: master, main, and main.

I believe the master is an old branch, but which of the two remaining main directories should I translate? Also, if possible, could you delete the master and the unnecessary main directory? Thanks!!

[steppi]

Thanks for pointing that out @AtsushiSakai. I’ll look into it today and start trying to clean things up. I’ve been keeping master around because it has translations for some strings stored in its translation memory that haven’t been propagated to main yet, but I think there’s a way to move those over automatically that I’ll try out.

[steppi]

@AtsushiSakai, sorry for the delay. It seems the reason for the duplication is that I gave @rgommers incorrect instructions for how to resync the numpy.org project in Crowdin to the numpy.org repo. Instead of syncing the numpy.org/main branch I'd migrated in such a way that it would receive updates to the source content, it created a duplicate copy which took its translations from the existing translations in the numpy.org repo. I'm contacting Crowdin support, and will try to figure out the proper way to sync to the repo.

[steppi]

OK, after consulting with Crowdin support, the following steps worked: Deleting the duplicated numpy.org/main folder in Crowdin (the one with translations imported from main), pausing the GitHub integration, closing the Crowdin PR, and finally resuming the GitHub integration.

Everything is working now. There is only one numpy.org/main branch which is receiving updates to the source content, and I translated a string into Spanish and verified that a corresponding commit was pushed to l10n_main. Things should be good to go for translating main.

I still need to keep the master folder around until I figure out how to export translations out of its translation memory. Chinese for instance is translated at 97% for master and 0% for main, but there's a lot of overlap in strings. I still need to figure out a good way to get all of those translations moved over.

[AtsushiSakai]

@steppi Thank you for your hard work. I confirmed the issue was solved and finished the remained translations.

[juanpabloduqueo]

Hi everyone,

I am new to contributing to open source software and I am interested in helping with the translation of NumPy's documentation into Spanish. I have read through the contributing guidelines, registered on Crowdin, and joined the NumPy project there to start assisting with the Spanish translation.

Could you please point me in the right direction on how to get started with this? Any tips, resources, or specific areas that need focus would be greatly appreciated.

Thank you for your guidance and support!

[melissawm]

Hi @juanpabloduqueo ! The first step is to go to https://scientific-python.crowdin.com, log in or create an account (you can use your GitHub credentials for this) and select NumPy (or any other project you are interested in) and start translating. These translations won't show up on the website immediately but will be merged later when a substantial portion (or even the whole site) is translated.

We are also in the process of expanding these translations teams so if you are interested, please join the Scientific Python discord server and the #translation channel specifically. Cheers!

[juanpabloduqueo]

Hi @melissawm! thank you for your recommendations! I have now started to contribute to NumPy's Spanish translation successfully and have joined the discord server :D

[SaeedForoutan]

Hi everyone. In January I started the process to migrate numpy.org to the Scientific Python Crowdin enterprise organization. However, this process wasn't completed, and all translations have still been carried out in the original NumPy Crowdin account. Today I'm going to complete this process and archive the numpy.org project in the NumPy Crowdin account. Going forward, all translations will be done in the Scientific Python enterprise organization. I hope the disruption will be minimal.

@SaeedForoutan, sorry for the long delay in responding. That's great that you want to help out. After I complete the migration described above, I can add Persian as a language to the project and reach out to you again about getting you invited to the Scientific Python Crowdin enterprise org.

Hi @steppi, I wanted to follow up and ask if the migration has been completed and if it's now ready to start the translation to Persian. Please let me know if there's anything specific I need to do.

[steppi]

Thanks @SaeedForoutan for following up! If you haven't already, go to this link https://scientific-python.crowdin.com/, and create an account following @melissawm's instructions above. I'll go in and add Persian as a language.

[SaeedForoutan]

Thanks @steppi, I have registered in the above link. Could you please invite me to the project so I can start contributing to the Persian translations? My username is the same as my GitHub username.

[steppi]

Thanks @steppi, I have registered in the above link. Could you please invite me to the project so I can start contributing to the Persian translations? My username is the same as my GitHub username.

Done

[SaeedForoutan]

Thanks @steppi, I received an invitation in my inbox for SciPy, not NumPy. I wonder if there might be some confusion.

[steppi]

Thanks @steppi, I received an invitation in my inbox for SciPy, not NumPy. I wonder if there might be some confusion.

Yes, just some confusion. I'm still getting familiar with Crowdin enterprise and didn't realize invitations were project specific; I thought I was sending an invite to the entire scientific python organization. You should have a NumPy invite now too.

[juanpabloduqueo]

Hi @steppi and @melissawm ! I've been working for a few days on the Spanish translation on crowdin for numpy.org. I misunderstood and performed translations on numpy.org and not Scientific-python. I am now following your instructions and registered for Scientific-python crowdin enterprise. However, I can't seem to find numpy to continue my translation work. Could you please send me a invitation link to the project so I can continue my work on the Spanish translation for numpy? My username is the same as my GitHub username. Thanks!

[steppi]

Sorry for the mix up @juanpabloduqueo. You should have an invite now. I'll ask Crowdin support about archiving the old numpy.org account to avoid things like this.

[juanpabloduqueo]

Hi @steppi! no worries. I lost some of the progress I had made on the old numpy.org when I switched to scientific_Python, but I am now at 71% again! Thanks for sending me the link! I will try to get this percentage as high as possible :)

[juanpabloduqueo]

Hi @steppi! I managed to get the spanish translation to 100% :D

[rgommers]

@juanpabloduqueo that is awesome, thank you! I'll note that @steppi is on holiday right now, hence the delay in you getting a reply. I hope @steppi or @melissawm will get back to you soon and we can get the Spanish translations deployed.

[juanpabloduqueo]

@rgommers it was a pleasure contributing to the project! Please let me know if you need additional help during the spanish translation deployment :)

[steppi]

Great work @juanpabloduqueo! I'm back from leave and will begin working on getting your translations deployed.

[melissawm]

Hello, folks!

We are happy to announce that we are setting up infrastructure for multiple project’s websites to be translated, including NumPy.org

You can read more in this blog post: Blog - Translations for Scientific Python projects 1

We also have some documentation at https://scientific-python-translations.github.io/

If you are interested in joining this effort, feel free to engage in ⁠the #translation channel of the Scientific Python Discord server where we can give you more info.

See you there! 🚀

[juanpabloduqueo]

Great work @juanpabloduqueo! I'm back from leave and will begin working on getting your translations deployed.

@steppi thanks! I look forward to contributing more. Let me know for whatever that needs to be reviewed from the spanish translation :)