Non-translatable strings are automatically marked in your localization projects when you import terms with a translatable="false" flag from an Android XML file.

Importing non-translatable strings

The terms import can be made in multiple ways:

• in the user interface, using the Import option in the Project page and selecting to import translations in the source language
• using our simple REST API with the method projects/upload, the argument updating and the value terms_translations. For the language argument choose the project's source language.
• with any of our code hosting integrations

When you import the non-translatable strings to the source language in your POEditor project, the source language needs to be set as Default Reference Language, otherwise the non-translatable values will be ignored.

After you import the untranslatable values in your Default Reference Language, they will be copied in all your other project languages and locked, so that they can't be edited.

Updating a non-translatable string

To update the source translation of a non-translatable string, you can either:

• update the value for that key in your source file and re-import it to the project, with the Overwrite existing translations option enabled
• edit it manually from the Terms page by disabling the Non-translatable option, making your changes, and then re-enabling it