Change the way we handle source strings updates

With the `update_without_changes`, previous translations are kept
even when the source string changed utterly. Using this option caused
some problems when updating source language strings, as the
translators do not get any notification, and the old translation keeps
approved, so translators do not have an easy way to find those strings
in Crowdin.

With the `update_as_unapproved` option, translators and Crowdin
managers can find those translations that need to be updated by
searching among not approved translations.

Quoting Crowdin's docs [1]:

> update_without_changes - preserve translations and validations of
   changed strings
> update_as_unapproved - preserve translations of changed strings
   and remove validations of those translations if they exist

[1] https://support.crowdin.com/configuration-file/#changed-strings-update
This commit is contained in:
Senén Rodero Rodríguez
2021-11-25 12:06:14 +01:00
parent b9ccfcf0ae
commit 30a0235ea3

View File

@@ -3,7 +3,7 @@ files:
translation: /config/locales/%locale%/%original_file_name%
ignore:
- /config/locales/**/rails_date_order.yml
update_option: update_without_changes
update_option: update_as_unapproved
languages_mapping:
locale:
ar: ar