30a0235ea3
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
23 lines
474 B
YAML
23 lines
474 B
YAML
files:
|
|
- source: /config/locales/en/**.yml
|
|
translation: /config/locales/%locale%/%original_file_name%
|
|
ignore:
|
|
- /config/locales/**/rails_date_order.yml
|
|
update_option: update_as_unapproved
|
|
languages_mapping:
|
|
locale:
|
|
ar: ar
|
|
ast: ast
|
|
ca: ca
|
|
es-ES: es
|
|
fr: fr
|
|
gl: gl
|
|
he: he
|
|
it: it
|
|
nl: nl
|
|
pt-PT: pt
|
|
ru: ru
|
|
sr: sr
|
|
sr-CS: sr-CS
|
|
val-ES: val
|