Phase 2 + 3 AI Only Translation Requests
Context
In order to get the dev environment for testing full of content so that it's similar as possible to production we've sent all Phase 2 and Phase 3 files, as well as any new content file that was not captured in the prioritization spreadsheet for translation using the AI only workflow. That means that these files will be processed through AI but we won't be making any edits to the translation memory.
All these files will go through the proper translation workflow.
All the translation of these files will be committed back to GitLab in Translation MRs as soon as the translation step on Phrase is set to "complete".
All the content in all the projects under /doc/architecture and /doc/development have been excluded from translation.
Translation Requests Overview
Here below there's an overview of the requests
gitlab project
Charts project
GITTECHA-66
Omnibus project
GITTECHA-67. Translation MR: gitlab-com/localization/tech-docs-forked-projects/prod/omnibus-gitlab!22 (merged)
Operator project
GITTECHA-68. Translation MR: gitlab-com/localization/tech-docs-forked-projects/prod/gitlab-operator!20 (merged)
Runner project
GITTECHA-69. Translation MR: gitlab-com/localization/tech-docs-forked-projects/prod/gitlab-runner!29 (merged)
How translations are generated
This recording from @mchrastek-ext shows a demo about how he's triggering the AI scripts once the Phrase project is being created. The team is looking into further automating this.