CrowdIn - Gitlab sync: Source strings in target file

Hi,

I have the following issue: I synced a huge translation update to our Gitlab repository while using the update_without_changes parameter. The idea was to be able to sync the update to the repo without the changes in the source that happened in the meantime causing the files to be incomplete, breaking up their synchronization.

That is why I used the update_option parameter with the value update_without_changes, so I could update the source while still being able to sync the translations.

However, another issue occurred instead: In files, where new strings were added in the interim, these source strings were now included in the target file, leaving me to have to delete them manually (or in some cases, manually look them up in our translation memory and insert the correct string where possible).

Is there a way to avoid these unwanted source strings in the target file? The one thing I can think of is that I need to set the export setting to “Export only approved translations” (which I hadn’t done as of now to account for source file changes).

Thanks!

Hi @mneustadt ! the option you used allows updating source text in your Crowdin project, by leaving the current translation. For example, you had the word Apple in the project translated to Norwegian as Eple and later you changed the source string on your repo to apple and update Crowdin file. The translation Eple will be kept

You mentioned that you synced translations from Crowdin to Repo, is that correct? not the source?

In files, where new strings were added in the interim, these source strings were now included in the target file - do you mean that after syncing translations from Crowdin to the repo you have source text instead of target language there?

If I got you wrong, please share some examples and the exact steps on sync process you did (like was it from project to repo or the other way around/source appeared on repo or in the project)