Let’s assume you have three country specific projects

  • England - English

  • France - English, French

  • Belgium - English, Dutch, French, German

Although you have different countries with their specific languages, English will be made available to all countries as well.

Based on such a setup, a few best practices may be identified.

Best practices might not meet your project setup and adjustments may be needed.

1. Human vs. machine translation

Machine translation services are well established and allow you to translate your content automatically and fast.

Human translators might work with machine translations as well but will proofread and translate making heavy use of their domain knowledge. Usually, they will be using translation software that enhances the translation process and allows for specific wording and corporate language. What is more, such software is able to detect already translated content and use the most recent version. That way, redundant work is limited and consistency increased throughout all translations - this also includes corrections that can be made used of automatically. This is a huge advantage, because machine translations usually do not have such a "memory" and each translation request is stateless.

You may also combine both approaches and have particular languages being translated using machine translations while others are to be translated by translation agencies.

2. Proofreading

Using human and/or machine translation has a huge impact on your proofreading process. With human translations, any proofreading should be happening during the actual translation process (usually, such software has specific proofreading workflows). That way, you can arrive at a "released" translation and consecutive translations can make use of this instantaneously.

With machine translations, your proofreading will usually take place in your content management system, because translationstudio translated and imports such content automatically. translationstudio itself does not provide any proofreading interface, although you could create such an interface in a custom process adjustment.

3. Content structure

Your content structure will curial and a certain project setup may derive from it automatically.

First and foremost, you will want to make sure that you reduce redundant translations as best as possible. Some

You will want to make sure that you do not mix country specific content with global content. Using the project setup above, it is save to assume that you will have English content that really is identical in all countries and some that might be specific to England. The same should be true to your French language content.

Therefore, it is probably a good idea to identify such global content languages and either have a single global project that contians those languages or have a master project (English) and translation projects where you translate English content into other global languages (typically French, Spanish, maybe German).

That way, you can make sure that you keep your content as separated as possible and you can either (1) publish such global content or (2) transport it into target country specific projects.

If you choose option (2), you will be able to add locale specific information to the global content.

Splitting projects into language and country projects may seem like over-engineering but you will want to take into consideration that pushing content specific to your "France" project into your "Belgium" project may cause inconsistencies and extra work, because you will have to make sure that such irrelevant content is never published - while this can be done at the beginning quite easily, it might be completely forgotten 2 month down the road.

4. Initiating translations

First, you will need to differentiate between content changes that are relevant for translations (typography) and changes that are not (change in wording, etc.). Your editors will be aware of this difference but it is good to be aware of such a difference when planning your translations.

A crucial aspect is to define your translation sequence:

  • Should a translation be submitted for all target languages (all at once)

  • Individual translations for individual target languages (separate)

While translationstudio allows for both scenarios, this choice might impact the number of translation options your editors are confronted with.

5. Immediate or quote based translations

translationstudio allows two types of translation scenarios:

  • immediate translations, where each translation request is being forwarded to translators as soon as they are submitted

  • quote based translations, where translationstudio stores your translation requests and only forwards them to translators once certain criterias have been met (e.g. minimum number of pages to be translated)

In a machine translation scenario, it does not make sense to use a quote based approach. However, with human translations, this may look different, because translation fees might apply "per translation project" (similar to cab fees upon entering the vehicle).

you can always use both approaches and implement changes at any time.