The github integration is filling all string translations from source language to target language on the wrong language

I have 2 language files. en-GB.json and de-DE.json. en-GB is the source, but if I modify a string in the german side, it adds all english translations to the german file in the PR created in github

Hi @AecoApp ,

From what I can see on my end, your source files and translation files are currently at the same folder level. It’s generally not recommended to store both in the same folder, as this can lead to issues where source files overwrite the translation files, which may be what you’re experiencing. I would suggest keeping the source and translation files in separate folders to avoid this problem.

1 Like

Hi @Olena , thank you for your reply. I added now a /source/_developer.json as a source and a /targets/%locale%.json as targets, where I have en-GB.json and de-DE.json. The _developer.json has the same translations as the en-GB.json, and the de-DE.json still gets overriden by the translations in the _developer.json. Perhaps I’m not understanding the role of the source file, should it be a file with the structure of the translation keys but not the actual translations? and then the actual translations in the source? Because the way we work is having the source also with translations, then the targets with the strings empty until we translate.

Hi @AecoApp,

Could you please share a project ID, so we can check what is going wrong?

Hi @oleh_crowdin , the project id: 728935

1 Like