Choose your translation strategy so that your translation units contain the right content for the translation management system.
Choose your translation strategy
Define your translation units. Do you need to send a single content item for translation or several of them at once? This depends on the way you structure your content. For example, information about products might live in individual content items, whereas web pages might be built from multiple content items.
A. Translation unit as a single content item
In some cases, you might want your translation unit to consist of a single content item. This would be the content item that triggered the translation process.
➕ Advantages
➖ Disadvantages
Easy to implement.
Content from a single identifiable piece of content will not be collocated in the TMS. This can lead to a worse experience for human translators or possibly worse results for machine translators.
If you want to translate the unit whole, you will need to trigger the process for all content items that are part of one identifiable piece of content.
B. Translation unit as all items in an identifiable piece of content
If you structure your content from multiple content items, you need to trigger the process for the root item. That is the root of your identifiable piece of content like a web page. Then traverse the children of the root content item.
➕ Advantages
➖ Disadvantages
The whole identifiable piece of content is translated together.
Easier for machines and especially human translators to see the context in which the content is used and create a better translation.
Harder to implement compared to a single-item approach.
Consider protecting content during the translation process
Protecting specific content item variants during the translation process might be beneficial to avoid errors.You can protect a variant by creating a workflow step such as Translation in progress where no user can make any changes apart from the integration itself. Then you need to move the variant to the workflow step. Once the translation is done, the process moves the variant to the next workflow step so that users can work with it again.
Protect the target variants
Target variants are those that you are translating to. Once the translation is finished, its result is written into those variants. Existing content, if the variants already exist, is overwritten. For this reason, we recommend protecting those variants for the duration of the translation process to avoid any data loss.
Protect the source variant
The source variant is the one you are translating from. There's a chance that someone will edit the source variant during the time after the variant was triggered for translation and before the translation process reads the data from the source variant, which results in unexpected data being sent for translation.If you protect the source variant:
The translation process is safe from modifications between the trigger and the process that is reading the data.
You can easily see all the item variants that are part of a translation process.
What's next?
Transform and translate content
Let’s take a look at the approaches you can take to maintain the original structure of your rich text elements in the translated texts.
Ensure your content is sent for translation just onceKeep in mind that you should protect all items that are part of the same identifiable piece of content. However, this change might trigger your webhook or Sync API listener again for all the child items.To prevent that, either set up your webhook to only trigger for the root content type such as Page, or, if using Sync API, filter only changes related to the specific content type.
