Setting up crowdin with multiple .json files

[lostdesign]

Hi everyone

I am in the process of setting up my repository for crowdin but happen to find some issues (probably due to my lack of knowledge)

My goal
I want to be able to use crowdin to translate .json files (see linked/src/locales at master · lostdesign/linked · GitHub) to make the process easier for translators.

I’ve added the GitHub integration and used the following branch configuration:
Source files path /src/locales/en-US.json
Translated files path /src/locales/%locale%.json

This seemed fine for me, however the PR by crowdin would overwrite all translated files with the source file? What did I do wrong? See New Crowdin updates by lostdesign · Pull Request #170 · lostdesign/linked · GitHub

When I look at the translations within crowdin, everything seems to be fine.

Link to crowdin https://crowdin.com/project/uselinked-app

Best,
André

[GregoryLanncved]

Hello @lostdesign probably this is the case similar to yours?

Consecutive commits translating back & forth from Portuguese (Brazilian) to English

@tbsprs just done a few tests from my side, most likely your behavior because both languages are pushed into 1 language. Try changing the configuration to include locale patterns: As a result, you should have 2 folders, one for pt-PT and another for pt-BR. You can also map languages, so as result there would be for example PT and BR (if you’re strict to 2 letters code).

Try checking export options, probably you’re using something, like “skip untranslated stings” or so. Also, I’d change the translation path to something, like /src/locales/%locale%/%locale%.json, because from your’s system doesnt know where the language folders should be (my assumptions)