Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork214
feat: add scripts that helps inserting Google-translated content into .po file#378
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
3940ad9
toee50c42
CompareThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Probably out of the scope of this PR, but eventually I think it might be useful to have a separatetranslation-tools
repo where to put tools that can be shared by different translation projects.
If the tools are in a separate repo, it is also not necessary to create a hidden dir that is not easily discoverable (using_scripts
might be a better option, unless it interferes with something).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I think we could merge it first, and create another PR for making batch procedure.
feat: add scripts that helps inserting Google-translated content into .po file
Uh oh!
There was an error while loading.Please reload this page.
[WHY]
As a translator, I'd like to have machine-translated content as the base that I can revise, which significantly reduces the translation effort.
[HOW]
Major
.scripts
directory, which is expected to be where all translation toolkits lie in. Poetry is set up here.One can run the script with:
Minor
from_cn.sh
script and move it into.scripts
.One can run the script with: