-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Write a script to sync translation in EN with other locales #3077
Comments
or it would be great if anyone can setup a free i18n management service, thing like https://localazy.com |
Yeah, I would also prefer a TMS like pontoon or weblate. I never tried localazy, but it looks fine too. |
Does this not already exist? |
It only allows to find untranslated words, not sync with the EN to remove staled words (words that in the other locales but get deleted in EN). We can extend to support this behavior |
I would like to set up inlang for Open-Assistant by just adding an Here is a preview, with a sample project: In addition, other useful tools are supported to make i18n easier like a VS Code plugin (in the next days) and a CLI. Let me know and I'll set it up for you 🙂 |
@NiklasBuchfink does it compatible with next-i18next? |
@notmd Yes, I have already set it up several times with |
@notmd I'm currently building a i18n-next plugin with inlang that users from i18n-next can use the inlang IDE extension to massively speed up their workflow and use the git-based online editor. 🎉 see https://inlang.com for more |
Then please help us setup, thank you! |
Looks very simple, just create a json file that defines the reference language: After that it should be able to use it with this URL https://inlang.com/editor/github.com/LAION-AI/Open-Assistant/ Only the i18n-next plugin plugin is missing rn, right? |
@stefangrotz That's right, the i18n-next plugin is currently under development. But there is also a json plugin that works for this use case. I still need to extend it a bit to support the |
@notmd @stefangrotz It took a little longer, but the time was used to optimize everything for a project like Open-Assistant. Now I have created the PR. Please let me know if I should change something. |
## Description This PR add the `inlang.config.js` and `@inlang/cli` to Open-Assistant to solve the issue #3077 With these changes, translators can manage translations in a no-code web editor and useful linting rules and machine translations can be used within the editor or via the `@inlang/cli`. I added a badge with the current translation status and a short description to the contribution guidelines. ### Preview **Editor** A live instance of the editor can be previewed with the following link: https://inlang.com/editor/github.com/NiklasBuchfink/Open-Assistant **Badge** [![translation badge](https://inlang.com/badge?url=github.com/NiklasBuchfink/Open-Assistant)](https://inlang.com/editor/github.com/NiklasBuchfink/Open-Assistant?ref=badge) ## Further information To check the status of the translations, exece `npx inlang lint`. Other useful command like `machine translate` and `open editor` your can find in the [docs](https://inlang.com/documentation/apps/inlang-cli). Within this week, the inlang VS code extension should also work ootb for `i18next` projects and helps extract messages and display inline annotations.
The script should accept an option locales params, example signature in TS
The text was updated successfully, but these errors were encountered: