When I export languages manually (or through the GitHub integration), strings that don’t have translations are falling back to the source language. For example:
My project’s export settings include the option to skip untranslated strings.
I see that some formats include the key, but with an empty string. This would be fine, although not ideal, but in this case the source language is just leaking through to the translated files.
Project ID is 825726
Hello @evaera,
Thanks for pointing this out!
I have just created the improvement task (CN-60385) for our devs team, for the users to be able to get only the key with an empty string after exporting files that have .toml extension.
Thank you once again for understanding!
The pictuerd Bulgarian localization file contains the English source text. This is unexpected: it should either be an empty string or the key should not be present at all. Note that my exported file format is TOML, if that’s a factor.
Thanks for the response. That would certainly be an improvement! But: having the key be omitted entirely would be better still.
Setting untranslated keys to an empty string will still generate needless changes and commits on the translated files, when their content hasn’t meaningfully changed. It would be better if the files were changed only when there was an actual update to their contents.
In the case of a nested structure like mine, TOML supports empty sections, which are essentially the same as an empty JSON object, so simply removing the key altogether still wouldn’t break the usability of the file.
I might be asking for a lot here - If I’m made to settle with empty strings, I’ll still be a happy camper. 
Hi @evaera , thank you, passing your additional information to devs and will keep you posted
