Fallback to source if strings are not approved

Crowdin Issues
1

We have enabled pre-translation for the strings in our source files. This means that as soon as we add a new string, it gets automatically translated into all our supported languages but remains unapproved. Additionally, we have a CRON job that runs daily to programmatically create, export, and download a translation bundle using the Crowdin JS SDK.

In our project settings, the ‘Export only approved translations’ option is activated, while ‘Skip untranslated strings’ is deactivated.

Currently, if a string is not approved, it does not appear in the downloaded files. However, I recall previously configuring a setting to download the source content as a fallback for untranslated or unapproved strings. For example, if the source language is English and a French translation is not approved, the downloaded file would include the string in English instead of omitting it entirely. Is this behavior still possible? I couldn’t find an option like ‘Use Source Strings as Fallback’ or anything similar in the settings.

2

Hi @cedric.trigoso

Unfortunately, we do not have an option to use Source Strings as a fallback once any of the export options are applied to the project. What I mean is that with the “Export only approved translations” option, unapproved translations are removed from the export.

As a workaround, you can consider disabling this option. Once no export options are enabled, the English source strings will be returned for untranslated strings on export.

3

Thank you for your answer @Olena.

With your solution, the source strings will be returned for untranslated strings, not for unapproved strings. I might look into a possible programmatic solution then.