-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Extract translation text and use AI to perform the translation #13411
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
base: master
Are you sure you want to change the base?
Conversation
1. add translate python tools; 2. translate current zh_CN text.
As discussed in the Issue this provides no mechanism for review. I'll go with what @hamishwillee says about being paranoid about blindly accepting translations not being a good idea. |
AI is anecdotally poor for technical docs. If it matters, you use humans. I think with flying robots it matters. A possibility though is to autopopulate every single string with an AI translation unapproved. Then only publish strings that are approved. This might make the translation process easier. That said, I'd rather stick with what we have - possibly adding AI integration to suggest strings though - if there is budget for buying the keys. |
I don't see that ability in the .ts file format spec. |
As I said in the issue
there are 2 functions for the python:
it does not care how you translate the text, by Crowdin or AI, and before you commit and push , you need confirm by |
You are missing the point that git diff is not the process we use to verify translations. We use Crowdin for that. Anyone can do translations on Crowdin, only certified approvers can approve those translations and only then do they come down in a pull request. Crowdin has full ui to handle that whole process. We can subvert that whole process with something new. Which is why I was looking at marking a translation as not yet approved in the .ts file. With that we could use the Crowdin approval process. But as far as I can tell it's not currently possible. |
|
I did a few tests, and it may be possible to import the files, forcing any changed values to be imported as unapproved (though we should only update those values in the file with AI values if they don't have translations). The question is if we want to. If we're not publishing values unless approved this does slightly reduce the work for translators, but I only see it as useful if the guessed translation by AI is good. Who knows. In any case up to you @DonLakeFlyer to decide if this approach is something you want to look more into. I don't have bandwidth to help for a while. |
Extract translation text and use AI to perform the translation.
Deails refer: #13410
Description
Test Steps
Checklist:
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.