My expected result which I can’t reach is that the source language export strings.xml are put inside res/values/strings.xml while the translations languages are in “res/values-LANG/strings.xml“ (which is correct right now)
you cannot have a single pattern that treats the source language as a static folder (values) and the translations as dynamic folders (values-%two_letters_code%). The source language export pattern must contain a placeholder that specifies the language to maintain the integrity of the bundle.
That’s too bad but thanks for clarification. It’s just a bit of annoyance because after downloading Android bundle I need to manually copy strings.xml from values-en to proper default values dir.
Hi, as a workaround, one option could be to automate that copy/rename step in your build or integration script so it happens automatically after pulling the bundle, but there is unfortunately no built-in Crowdin setting that would remove the -en from the source folder name.