We might want to switch from our current setup:
- a user proposes a translation
- once another user votes for the translation it get committed
to latest Weblate's feature of translation states.
This might be needed in order to be able to build a staging website. (It'll also involve having weblate use two Git repositories, one to store all translations, one to store only the reviewed translations -> we'll have to see how to make this happen, likely we'll have to query it's database directly and add the corresponding commits.)
However, it seems that these translation states always commit and modify the PO files. And the states are only stored in Weblate's DB. This is what we want to verify.
#7 Updated by u over 1 year ago
As we have a working script to extract suggestions, we can very easily stick to our current setup. In particular as the translation states are only stored in the DB → and thus here again we would have to modify our current script to extract these states instead of the suggestions.