Skip to content
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

Explore our crowdin integration options #7121

Open
bmuenzenmeyer opened this issue Oct 15, 2024 · 3 comments
Open

Explore our crowdin integration options #7121

bmuenzenmeyer opened this issue Oct 15, 2024 · 3 comments
Assignees
Labels
i18n Issues/PRs related to the Website Internationalisation infrastructure Issues/PRs related to the Repository Infra

Comments

@bmuenzenmeyer
Copy link
Collaborator

bmuenzenmeyer commented Oct 15, 2024

The GitHub sync process - visible at #7089 is nice but has led to maintainer noise and some manual interventions.

This ticket should explore the use of:

From Andriy

Translations made via In-Context will be saved to your Crowdin project and then synced back to GitHub via connector or GitHub Action

Using both might create the best experience.

demo at https://demo.crowdin.com/

I want to make sure any live integration doesn't impact site performance or security.

@bmuenzenmeyer bmuenzenmeyer added i18n Issues/PRs related to the Website Internationalisation infrastructure Issues/PRs related to the Repository Infra labels Oct 15, 2024
@bmuenzenmeyer bmuenzenmeyer self-assigned this Oct 15, 2024
@AugustinMauroy
Copy link
Member

Can we can just to a script that we trigger with a cron job, that create a commit with all transition ?

@bmuenzenmeyer
Copy link
Collaborator Author

I dont like a custom approach - I'd rather use vetted, version-controlled tools. The GH Action has a lot of configurability and the support of Crowdin. A custom cron would eventually resemble the action, I suspect.

@dies
Copy link

dies commented Oct 16, 2024

Integration via Github Action is definitely a great idea! It's a recommended way to integrate Crowdin with Github. By the way, you can reuse your crowdin.yml. Please let us know if we can help you with the transition.

As for in-context, this technology is really useful for translating product copy, such as UI menu items and button titles, which are super hard to translate without context. Since you're translating MDX, each page itself carries enough context, they're perfectly fine to get good quality translations when translated in Crowdin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n Issues/PRs related to the Website Internationalisation infrastructure Issues/PRs related to the Repository Infra
Projects
None yet
Development

No branches or pull requests

3 participants