Translation Workflow

Every translatable string in Ownlate is a segment. A segment holds the source text and all its translations across every target language. Understanding how segments move through statuses is the core of working with Ownlate.

Segment statuses

Status	Meaning
`untranslated`	No translation exists yet
`draft`	Translator saved a work-in-progress
`in_progress`	Translation was rejected and needs rework
`needs_review`	Translator submitted — awaiting review
`reviewed`	Reviewer approved — awaiting final sign-off
`approved`	Fully approved and ready to ship
`outdated`	Source text changed after approval — needs re-translation

untranslated → draft → needs_review → reviewed → approved
                            ↑               ↓
                       in_progress ← rejected

When the source text of an approved segment changes, all its translations are marked outdated automatically.

The editor

Open any project, then click a segment to open the editor. You’ll see:

Source text — the original string your developers wrote
Context — optional URL and screenshot attached by the developer
Translation Memory suggestions — fuzzy and exact matches from previously approved translations, shown with a match score
Glossary highlights — terms from the workspace glossary are underlined; hover to see the definition and preferred translation
Plural forms — if the segment is plural, separate input fields appear for each form (zero, one, two, few, many, other) depending on the target language

QA checks

Every time you submit a translation, Ownlate runs automatic quality checks:

Missing interpolations — variables like {{name}} or %s present in source but absent in translation
Extra interpolations — variables in translation not present in source
HTML tag mismatches — unbalanced or missing HTML tags
Trailing whitespace
Same as source — translation identical to source text (flagged as a warning)
Forbidden terms — terms marked as forbidden in the workspace glossary

Custom regex QA rules can be added by admins in Workspace → QA Rules. Each rule has a severity: error (blocks submission), warning, or info.

Translation Memory

When a translation is approved, it is automatically saved to the workspace Translation Memory (TM). The next time a segment with similar source text appears, the editor shows TM suggestions ranked by match score.

You can also run Pre-translate on a whole project to bulk-fill segments using TM matches above a configurable score threshold before your translators even open the editor.

Bulk actions

In the segment list you can:

Filter by status, language, file, or search term
Bulk approve all reviewed translations for a language
Bulk reject with a reason

Roles in the workflow

Action	Required permission
Save draft / Submit translation	`translation:write`
Review (`needs_review` → `reviewed`)	`translation:approve`
Approve (`reviewed` → `approved`)	`translation:approve`
Reject	`translation:approve`

Owners and admins have translation:approve by default. Translators have translation:write only.

Tasks

Use Tasks to assign work to specific team members. A task can be of type Translate or Review, scoped to one or more languages, with an optional due date. Task status changes trigger notifications to assignees.