Thank you, that seems to have worked! For the record and for anyone else experiencing similar problems, I disabled English (en) as a translation language only for this file, ran crowdin download again, and it worked with no other changes. However, changing the target language seemed to remove all existing translations for that file and I had to repopulate them with pre-translation and Translation Memory, which was fine but not ideal.
However, I think these are problems you at Crowdin should be handling on your end. An .xcstrings file specifies which locale is the source locale in the sourceLanguage attribute, so a Crowdin manager like me should not need to tell Crowdin that it should not be writing translations to that file for that locale.
FWIW, after trying to get this xcstrings integration to work correctly, I have three changes in functionality I’d like to request:
- Crowdin should never write translations to an xcstrings file for the locale specified in the
sourceLanguageattribute of that file. multilingual: trueshould be the default configuration for xcstrings files, i.e. authors of crowdin.yml config files should not have to specify that because xcstrings files are always multilingual.- Crowdin should automatically hide from translators any strings in an xcstrings file that specify
"shouldTranslate": false - If the above cannot be changed, these requirements should all be documented (maybe at https://store.crowdin.com/xcstrings)