Avoiding untranslatable text to be added to TM
Panagiotis Kavrakis avatar
Written by Panagiotis Kavrakis
Updated over a week ago

You can always clean up your TM regularly to ensure it's accurate with no outdated entries.

If you cannot avoid sending the strings that don't need to be translated to Transifex, you can tag them as “Locked” so translators won't be able to translate them:

  • Find all the strings with the key "_notrans"

  • Assign the 'locked" tag to them.

You can tag the strings in the Editor, one by one, in bulk (filtering by Key), or via API.

If the file format is .xliff, .po, .xml, and the translation files are pulled from Transifex using the mode "sourceastranslation", the files will include the translated strings. The untranslated ones will be filled with the corresponding source strings.

However, if the resources are in the .plist or .string file format, the default mode will work (download translation files for use).


Looking for more help? Get support from our Transifex Community Forum!

Find answers or post to get help from Transifex Support and our Community.

Did this answer your question?