Translation Workflow
The process and steps involved in translating content from creation to publication.
Definition
A translation workflow defines the sequence of steps content goes through from source creation to published translation. Typical stages include: string extraction, translation assignment, translation, review/QA, approval, and publication. Modern continuous localization workflows integrate with CI/CD pipelines for automated sync between development and translation.
Examples
- →Basic: Extract → Translate → Review → Publish
- →Enterprise: Extract → Assign → Translate → Review → QA → Legal → Approve → Publish
- →Continuous: Push code → Auto-extract → Translate in TMS → Pull → Deploy
- →Crowdsourced: Submit → Community translate → Vote → Approve
Frequently Asked Questions
How do I set up a translation workflow?
Steps: 1) Define stages (translate, review, approve) 2) Assign roles (translator, reviewer, PM) 3) Set up automation triggers 4) Configure notifications 5) Establish quality gates. Start simple, add complexity as needed.
What's the difference between waterfall and agile localization?
Waterfall: translate all content in batches before release. Agile/continuous: translate incrementally as content is created. Agile is faster, enables parallel development, but requires automation and may ship with partial translations.