I’m using Apple .xcstrings string catalog multilingual files. The underlying format is JSON. It seems that Xcode adds spaces right after the keys whereas Crowdin does not, which can be a cause of noisy diffs in Git and potential merge conflicts.
Could Crowdin please be fixed so that it adds an extra whitespace after keys so that it conforms to what Xcode outputs? Thank you.
Unfortunately, I cannot see the file changed because the diff is too large. Just to clarify, if you download the translations from the UI, the spaces after keys will not be removed? Could you please check?
It seems like there might be an issue with the synchronization process. Could you please provide some extra information that will help us understand the problem more clearly and find a solution for you?
A sample of the source file you upload to Crowdin.
The translated file you receive as a translation from Crowdin.
The project ID where you are working in Crowdin.
You can send us the file samples directly, just email them to support@crowdin.com
Alternatively, just let us know the project ID so we can check system logs from our side; this will shed some light as well
Hello!
We are facing the same issue. When we’re using GitLab integration to update localizations in our repo, Crowdin generated .xcstrings does not have additional space after localization key, whereas Xcode generated does.
Could you fix this please?