Wordbee Translator includes some "out of the box" workflows that you can use to run complex workflows such as transcreation, back translation or parallel proofreading tasks.
Once the last supplier in the workflow has finished the task, the deliverable will be ready to be handed over to the client.
| Table of Contents |
|---|
Example of a transcreation project
This is an example of a transcreation project where EN texts need to be created in FR.
We have two vendors already working on the French texts and my system admin will hand over the final version to the client.
This is how the jobs will be presented in the CAT Editor:
> The first transcreation task serves to propose version A texts for the target language.
> The second transcreation task serves to propose version B texts for the target language.
> The reconciliation job presents Version A and Version B of the French texts to the user in charge of creating the final version of the deliverable. The last FR(v3) column will contain the final texts and the transcreation project will be delivered to the client.
| Info |
|---|
Take advantage of the Multicolumn Editor to have all the essential information visible while you are working on the job. You can customize the Editor layout to fit your project and task. For example, during reconciliation I may want to display additional comments from each of the versions of my French texts, the Source language (EN) or whatever information you may find relevant to complete the task. |
How to set up a transcreation project
| Table of Contents | ||
|---|---|---|
|
Set up your workflow
Before setting up the project, you may need to enable relevant task categories in the system such as transcreation, back translation or reconciliation. In a given workflow template, you will find them under the "presets" option under the work steps section in the workflow templates. You can rearrange the tasks in your workflow as needed.
To set up a simple Transcreation workflow, you could proceed as follows:
Step 1: Choose the right preset workflow
Open your Codyt project and edit the Project Settings
Go to Work steps > Preset workflow and select the Back translation (2 parallel translations) workflow. You can adjust the workflow to your own needs.
Step 2: Replace the "translation" tasks by "transcreation"
When adding the new workflow categories, make sure you choose the same direction of source and target languages as it was defined for translation. Each of these tasks will serve to propose alternative texts during the "reconciliation" step.
In the screenshot below, you can see the relevant tasks of the default workflow.
You can change the default workflow by adding the new task (each time selecting the right source and target language), as highlighted below:
Step 3: Remove the tasks you do not need
In this example, we need to remove the tasks proposed after back translation and back validation.
Update the supplier services and pricing details
Since new tasks have been enabled in the system, you will need to update the service portfolios of your inhouse team and/or external suppliers to be able to perform these new jobs.
For inhouse teams, you will need to add the service in the user profiles, whereas supplier companies carry their services in their price list. If you wish to be able to invoice these jobs to your clients, then you will also need to update client price lists too.
Customize your Editor Settings
Transcreation workflows may require a bit of creative writing. That is why we recommend disabling the auto-propagation option in the Editor that allows you to keep translations "uniform". If you require to have different versions of a translation, than you should switch off the auto-propagation featureoffers you the option to choose a translation workflow for Standard projects that includes a pivot language.
A pivot language, sometimes also called a bridge or relay language, is a language used as an intermediary language for translation between many different languages – to translate between any pair of languages A and B, one translates A to the pivot language P, then from P to B.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
How to set up a pivot language translation workflow
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
To set up a simple Pivot language workflow, you could proceed as follows:
Step 1: Choose languages when creating new Standard project
When creating a new Standard project and choosing your source and target languages, you can choose one of the target languages to act as a pivot language.
Once you have decided on what tasks the project will contain, click Save.
Step 2: Choose preset workflow
Go to Project details > Workflow & Suppliers and click Edit.
Choose the preset workflow from the drop-down menu available next to Work steps. All the preset pivot language workflows have been marked with a red outline in the screenshot below.
In this example, we will choose Pivot: Translate and revise with 1 pivot language.
This will leave us with the workflow you can see on the screenshot below, where the information on the direction of the tasks is marked with a red outline.
Step 3: Add documents to translate
Go to Documents and add the documents you wish to translate under the appropriate source language folder (in this case, Japanese).
Step 4: Create jobs based on the preset workflow
Go to Jobs, click on New workflow and choose the option Create jobs based on a workflow.
In the next window click on Select multiple languages and tick all the languages that are part of your project to create the corresponding jobs.
Step 5: Choose suppliers (dependencies)
After completing all the previous steps, now you can choose the suppliers for the jobs in the workflow
You can see all the jobs created based on this workflow and by clicking on the link icon next to the description of the task, you can see the dependencies.
In the screenshot above, we can see that the job with reference Pivot language workflow in Standard/5 (English to French translation task) includes the following dependencies:
In order to start this task, as Japanese is the original source language and English is the pivot language, the Japanese to English translation (job with reference Pivot language workflow in Standard/4) task needs to be finished.
In turn, the end of the English to French translation task is a prerequisite to start the job with reference Pivot language workflow in Standard/7 (which is the English to French revision task).
Since these jobs have these clearly marked dependencies, this provides you with a convenient way of planning your project.
You can inform your suppliers of the tasks you have in store and they can plan ahead, while the actual tasks will be on hold until the previous jobs listed in the dependencies are completed.