1552804 - [pre-translation] Save pre-translations as "Fuzzy.Next"

Status: RESOLVED FIXED

(Webtools Graveyard :: Pontoon, defect, P3)

Description

[Matjaz Horvat [:mathjazz]]

Storing pre-translations in VCS is easy, but it requires translations status changes in order for humans to post-review pre-translations. Here’s a possible implementation:

We replace the Fuzzy status with a new status "under" the Translated level (say "Fuzzy.Next"). Strings in this status end up in VCS, but still "need some work", which is true for both, the current Fuzzy status and the pre-translated strings.

So finally, we'll have Missing < Unreviewed < Fuzzy.Next < Translated as the available translation statuses. Humans will only be able to make Unreviewed or Translated submissions, while machines will only make Fuzzy.Next submissions.

Of course, humans will be able to approve Fuzzy.Next, which will make them Translated.

Note: we'll also need to run checks on pre-translations once we start storing them as "Fuzzy.Next".

Comment 1

[Matjaz Horvat [:mathjazz]]

Most of the work for this bug has been done already as part of https://github.com/mozilla/pontoon/pull/1573.

We store Pretranslations as "Fuzzy", which means they are synced to VCS (i.e. can be used in product) and flagged as "needing work" to localizers.

There's followup work needed though and we track it under bug 1666320.