Bosca / Localization

Workflow

Draft to published, on the record

A translation isn't done the moment it's typed. It moves through a defined set of states, with the invalid jumps blocked, its origin recorded, and every change kept — so what reaches production has been through the checks you expect.

The states

Seven states, and only valid moves

Each translation sits in exactly one state, and the workflow only allows the transitions that make sense — you can't publish something that was never reviewed.

Draft

Being written or edited.

AI-generated

Produced by AI, awaiting review.

In review

Submitted for a human check.

Approved

Signed off, not yet live.

Published

Live, and ready to export.

Rejected

Sent back for changes.

Archived

Retired from active use.

Origin & review

Know where every word came from

Each translation records how it arrived. That matters most for AI: anything marked as AI-generated enters a state that can't be published without a human review first — so machine output is always checked before it ships.

  • Origin is one of human, import, sync, or AI.
  • AI-marked work lands in its own state and must pass human review.
  • Editing an approved or published translation sends it back to draft.
origin
HumanTyped by a translator.
ImportBrought in from a file.
SyncPulled from an external tool.
AIMarked, and held for review.

Every change kept

An audit trail you can trust

Nothing is silently overwritten. Every state change and every text edit is written to an append-only history — who did it, where it came from, and the text before and after — across strings, plurals, and documents alike.

  • Each entry records the state change and the text before and after.
  • The actor and the origin are stamped on every change.
  • One history spans strings, plural forms, and documents.
history · checkout.pay · de
ai-generated → in reviewAda
in review → approvedSam
Jetzt zahlenJetzt bezahlen

Keep exploring

More on Localization