Skip to main content
The Translations tab is where the work happens. It’s a spreadsheet-like grid: one row per key, one column per language, plus the source language for reference.

​
The translation grid

  • Each row is a translation key (e.g. checkout.placeOrder), shown as a nested tree using the project’s key separator.
  • The source column shows the original text you’re translating from.
  • Each target column holds the value for one language.
  • Click any cell to edit it inline. Save with Enter (or the save control); cancel with Escape.

​
Cell states at a glance

Cells are visually marked by status so you can see progress at a glance:

​
Adding and editing keys

  • Add key — create a new key with its source text. Optionally add tags and a description.
  • Edit key — rename a key, change its tags/description, or attach screenshots.
  • Delete key — removes the key and all its values across languages.

​
Key details panel

Open a key’s detail panel to see and manage everything about it in one place:
  • Description — context for translators.
  • Screenshots — in-context previews of where the string appears. See Screenshots.
  • Tags — for grouping and filtering.
  • History — every prior value, with author and approver. See History & Rollback.
  • Suggestions — glossary and translation-memory hints.

​
Suggestions while you translate

As you edit a cell, TextSetu surfaces help automatically:
  • Glossary suggestions — for terms in the source text, the approved translation (or a do-not-translate / forbidden warning). See Glossary.
  • Translation memory suggestions — previously translated sentences that match the source (≥75%), so you can reuse prior work with one click. See Translation Memory.
  • Quality warnings — automatic QA checks flag issues like mismatched placeholders or forbidden terms.

​
Plurals

A key can have plural forms (e.g. one / other) when a language needs different wording depending on a count. Each plural form is translated separately, and TextSetu respects the plural rules each language requires (some languages have only other; others have several forms).

​
Tags and filtering

Use tags to group related keys (e.g. checkout, email, legal). Open the Filters panel (the funnel icon next to search) to narrow the grid — it slides in from the side and offers:
  • Source text contains and Scope prefix — text/prefix matches.
  • Missing in — keys with no translation in a chosen language.
  • Approval status — Approved / Pending review / Draft (when approval is on).
  • Outdated only — keys with values flagged outdated.
  • Tags and Sort by.
Active filters appear as removable chips below the search box; Reset all clears them at once. Several dashboard cards (Outdated, and the Approval Status cards) deep-link into the grid with the matching filter already applied.
The source language column shows a “missing” count of keys with no source text — more useful than a completion percentage, since the source is what everything else is translated from.

​
Screenshots

Attach a screenshot to a key so translators can see exactly where the string appears in the product. Open the key’s detail panel and upload an image; it shows as an in-context preview. This dramatically improves translation quality for ambiguous short strings (a lone “Open” means different things in different places).
Screenshot upload requires media storage to be enabled for your organization.

​
Submitting changes for review

If the project has Approval required on and you’re not an approver, saving a value creates a proposal (status pending review) instead of publishing it. An approver then reviews it. See the Approval Workflow. If approval is off, or you have approver rights, your saved values are published immediately.
Related: Approval Workflow · Glossary · Translation Memory · Quality Checks