Workflow

Context / Screenshot

Visual or textual information showing where and how a string is used.

Definition

Context in translation refers to additional information that helps translators understand how a string is used in the application. This can include: screenshots showing the UI, descriptions explaining the feature, character limits, placeholders, and related strings. Good context dramatically improves translation quality by preventing ambiguity and mistakes.

Examples

  • Screenshot showing 'Save' button in a modal dialog
  • Comment: 'This appears in the checkout flow after payment'
  • Max length: 20 characters (button label)
  • Related strings: 'Cancel', 'Save and continue'

Frequently Asked Questions

How do I add context to translations?

Methods: 1) Add descriptions in code comments (extracted by CLI) 2) Upload screenshots to TMS (IntlPull supports this) 3) Use descriptive key names 4) Add context fields in translation files (ICU supports @description).

Is context really necessary?

For quality, yes. 'Save' could be a verb (button action), noun (game save), or adjective (save mode). Without context, translators guess. Poor translations lead to user confusion, support tickets, and retranslation costs. Context is investment in quality.

Related Terms

Ready to simplify your i18n workflow?

Start managing translations with IntlPull.

    Context / Screenshot - Definition & Examples | IntlPull Glossary | IntlPull