Translation workflow
Your translators get the work. The project stays with you.
Prepare a task for each translator and proofreader, take the results back, and let statuses decide what goes out and what comes in. We recommend Translator Edition for translators: it is included with every Localizer license.
- Who translates
- Your translators, an agency, machine translation
- They get
- A translator project, a Delivery Bundle, XLIFF 1.2, or CSV
- Recommended
- Translator Edition, included with every Localizer license
- Back in the project
- Import Translation Results, statuses included
Who translates?
Statuses decide what goes out and what comes back.
Translator Edition
The recommended way to work with translators.
Translator Edition is included with every Localizer license; available features follow the main license. Translators cannot create projects, add files, or prepare tasks: the project stays with you.
- The translated UI in the visual preview
- Validation when the translator saves
- Localizer's own statuses, from Not translated to Complete
- The most exact import: the translator project is merged like a new build, even if the application has changed a lot since you sent the task
A Delivery Bundle is a folder with the translator project, the Lingobit setup, a README with the steps, and any files you add, such as a glossary or screenshots.
The next release sends only the changes.
Of 10,000 translated strings, Scan for Changes finds the 20 new and 5 changed ones, and the next task holds only those 25. You pay to translate and proofread 25 strings, not 10,000.
If a translator has started on the old project, Import Old Project in Translator Edition carries that work over; an old translation replaces a new one only if its status is higher.
What Translation Workflow does and does not promise.
Handoff workflow is one part of the project, not the whole localization process.
What Lingobit helps with
- Translation and proofreading tasks chosen by status
- Translator Edition, XLIFF 1.2, and CSV exchange
- Validation when translators save
- Importing results with their statuses
- Sending only the changes after the next build
What remains project-side
- Choosing translators and reviewers
- Deciding what content is safe to translate
- Reviewing imported translations
- Running final localization QA
- Generating and verifying localized output
- Vendor management and contractual translation responsibility
Related capabilities
- PreparationMove strings into resources, lock technical strings, and test with Pseudo Translate before translation.
- Visual localizationVisual context and previews, so translation decisions stay connected to the UI.
- Translation assistanceMachine translation, translation memory, Translation Hints, duplicate reuse, terminology, TMX, and TBX.
- Localization QAValidate completed translations, run spellcheck, and use Crash Finder where needed.
- Release workflowScan the next version, reuse translations, automate steps, and create localized files.
Send the work out. Keep the project.
Prepare translation tasks, exchange them through Translator Edition, XLIFF, or CSV, and import the results with their statuses.