Translations: How do the links resolve when things are (i think) hosted on crowdin

[lwasser]

I'm curious if @flpm can help us here. Felipe, I was able to login and join the allcontributors crowdin project.

https://crowdin.com/project/all-contributors

What I don't understand is where the translations are hosted (or were hosted) when the website was built and how we should move forward when we get the website online.

Right now I think we are considering moving to github pages for publishing.
I was able to get the website landing page online here: www.leahwasser.com/all-contributors

But docs would go to a version of the website in the correct language. Right now the index page is hard coded to go to docs/ (it's broken online because i don't know how the translation magic works and where that link should go so the correct language appears for the user.

Are you able to share any insight into how this might be setup by chance?

[flpm]

Sure, I am happy to help, I will take a look

[flpm]

Looks like it downloads the translation files when it builds the docs, using build-with-translation.

It calls a crowdin-upload to update the translation templates with changes, then crowdin-download that probably downloads the translation files and then builds.

The upload and download is handled by the Java crowdin-cli, which is on /crowdin/crowdin-cli.jar

I will give it a try tomorrow.

[flpm]

I was able to run the build and build with translations, but it does not get the files from Crowdin because I don't have the API key and the project ID:

crowdin.yaml

project_identifier_env: CROWDIN_DOCUSAURUS_PROJECT_ID
api_key_env: CROWDIN_DOCUSAURUS_API_KEY

[lwasser]

@flpm I added you to Crowdin yesterday 🚀 I just got access myself so I haven't yet tested creating an API key. But please let me know if that helps you build things locally. I think our goal is to build translations in CI (potentially) but I really would love to understand how you think this should work as I don't fully understand how a user discovers translations in their browser!!

[flpm]

Thanks Leah! I was able to login.

Yeah, I think in the current setup the translations are downloaded and built in CI only.

I tend to prefer having the translations in the repo, where you have full control over the existing work. Imagine the situation where Crowdin is acquired and decides to shutdown the account or the service. You risk losing everything. Now, realistically, chances are low, but you never known, the incentives of the project and the company are not exactly aligned.

[lwasser]

@flpm that makes a lot of sense. It would be nice to have them synced to the repo via a cron job!

Oddly with crowdin the same thing happened to me! Maximilian added me and I didn't see a notification. Can you please try to login to the platform. You should see that you are added to the project now as a manager.

[flpm]

I was able to login with my GitHub account and had access to it! I was able to generate an API token and now I am exploring the CLI

[lwasser]

Fantastic!! Thanks @flpm 🎉

[lwasser]

https://all-contributors.github.io/all-contributors/

We have a landing page 🚀 for the website!!

[lwasser]

@all-contributors please add @flpm for translations

[allcontributors]

@lwasser

I've put up a pull request to add @flpm! 🎉

[flpm]

After playing around and rewriting the config, I was able to build locally with translations using the Crowdin client from the NPM package (which would also address #855).

But it is still very messy and some languages have issues, I will continue working on figuring out exactly what's going on.