Non-translatable content
Learn about types of content that you may not want to translate.
Types of non-translatable content
While planning the localization of your project, it's important to identify fragments
that you don't want to translate. These can include the following:
- Proper names, such as brand names.
- Contact details (though you may need to translate some details, for example country names).
- UI text (if the UI has not been localized).
- Code blocks (but you may want to translate comments in the code).
- Legal text (you may need to handle it separately).
Tip: You can use glossaries to let translators know which phrases they shouldn't
translate.
UI text
If your project contains UI terms, it's important to know whether the UI has been translated, and into which languages.
If the UI hasn't been localized, you should let translators know how to handle UI
text. For example, you may want them to follow each UI term with its translation in
brackets.
| English source | Polish translation |
|---|---|
| Click New wand. | Kliknij New wand (Nowa różdżka). |