Pretranslations are assigned translation status Fuzzy, which allows us to: 1. Immediately send them to version control system. 2. Make them available in the product. 3. Inform localizers that they should be given another look. 4. Run quality checks on them to identify any errors or warnings. The caveat however is that translation status Fuzzy is also used for [fuzzy](https://www.gnu.org/software/gettext/manual/html_node/Fuzzy-Entries.html) translations of the Gettext system (filenames ending in .po), which are **not** used in the product. That means bullet point #2 isn't accurate for projects using the Gettext system - pretranslated strings in .po files will not make it to the product unless human translator approves them. We should mitigate that.
Bug 1666320 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Pretranslations are assigned translation status Fuzzy, which allows us to: 1. Immediately send them to version control system. 2. Make them available in the product. 3. Inform localizers that they should be given another look. 4. Run quality checks on them to identify any errors or warnings. The caveat however is that translation status Fuzzy is also used for [fuzzy](https://www.gnu.org/software/gettext/manual/html_node/Fuzzy-Entries.html) translations of the Gettext system (filenames ending in .po), which are **not** used in the product. That means bullet point #2 isn't valid for projects using the Gettext system - pretranslated strings in .po files will not make it to the product unless human translator approves them. We should mitigate that.