Set up a translation project
-
Projects → Create project. Name it on the Project Name tab.
-
On Labeling Setup, open Natural Language Processing and pick Machine Translation. The template shows the source text next to a
TextAreafor the translation. -
In the config, change the two
Headervalues to your language pair and rename$englishto match your data column (e.g.$source). -
On Data Import, upload a CSV/JSON with one row per sentence — the column name must match the
$variablein your config. Save. -
Optional — Translation Memory and glossary: Project → Settings → Translation (the tab appears on any project whose config has a
TextArea). There you can:- add TM segments by hand, Import TMX / Export TMX, or Backfill from translations already made in the project;
- maintain a Glossary of preferred terms, with auto term extraction;
- toggle Show inline suggestions to annotators and scope the suggestion sources (this project / entire organization / selected projects). Suggestions appear under the translation box while annotators type — click to fill.
Full card-by-card reference: Translation settings.
Go deeper​
- Translation settings → — TM CRUD, TMX import/export, backfill, glossary + auto term extraction, suggestion scoping
- Import data → — CSV/JSON formats, cloud storage
- Configure labeling interface → — customize the template
- RTL / non-Latin scripts → — bidi-correct rendering for Arabic-script and other targets
- Export annotations → — get the finished pairs out