![]() |
| Technical view of Localization
Workflow- The flow of information between authoring and release management. |
"Localization Workflow" in ]project-open[ refers to a number of steps to create a localized version of product such as a web site or a computer program.
]project-open[ supports several aspects of L10n WF:
Please note that ]project-open[ does not deal with the technical steps of preparing a L10n Kit or integrating the translation results into the target repository.
![]() |
| The L10n Project Cycle - A detailed list of processes related to the (comercially) successful completion of a L10n project. |
The "L10n Project Cycle" extends the technical part of the L10n WF by administrative and commercial activities such as quoting, staffing, invoicing and controlling. The actual (technical) L10n WF is only part of it.
]project-open[ supports the project cycle by means of several modules such as Invoicing (semi-automatic generation of purchase orders and invoices), Freelance Database (manging translator's skill profile, staffing suport, searching, ...) etc. Please click on the diagram above for details.
![]() |
| Schematic view of the translation workflow.
]project-open[ replaces Email communication by upload and download over the Internet, eliminating the usual file transfer issues. |
The "Translation Workflow" is only a small part of the total L10n Workflow and refers to the communication between translators, editors and proof readers across geographica and organizational boundaries.
]project-open[ supports the translation workflow by means of its Translation Worflow Engine. The workflow is driven by the download/upload actions of the translators and editors, freeing up the project manager's from sending and receiving emails with file attachments.
Do you have feedback, questions or suggestions? Localization Workflow is an intensively discussed subject today and the above is just our definition of terms and processes. We would highly appreciate your feedback.