DeepL Translation process

• The DeepL process is connected directly to creating a country-related language layer
• It then directly translates page title and url path
• values of general config areas like title, meta data, teaser information is directly translated when creating a new language layer
  except it is connected to typo3 flex forms which are labeled as “plugin options”.
• You can then use the “translate” as well as “copy” process. Both will directly translate the content elements.
  Difference is that “translate” creates “connected” mode and “copy” as usual free mode.
  We recommend to use “copy” and the free mode now being able to work with DeepL Translations.
• If you want to use a copy process without direct DeepL Translation, it can be switched off per page by using the green click element on top of the page.
• There are still some elements which can’t be considered by the DeepL Translation process which are connected to so called “flex forms” in typo3.
  
  In our Zehnder CMS systems they are mainly visible as “Plugin options”.
  Exemplary content elmements which still need to be translated by hand are:
  • CTA element
  • Compare Table
  • HotSpot element
    
    in general each element that is maintained in the “list” view in typo3 BE or which has “plugin options” within the edit mode.
  • In case a page with a plugin has been translated, please make sure that the plugin maintained an the right plugin elements in right langauge are connected to the related language version of a page.

Important:

A page should be translated in the local tree and not in a master tree and then copied to another tree.

So workaround would be:

1. to create the master page in EN in a master tree
2. copy the master page from EN layer in master tree to EN layer in country tree
3. translate page to country language
4. translated content elements can be revised as usual
5. Every deepl based translation should, as usual, be proofreaded.
    

Your editors all should have access now to use it in their trees.

Above all:

To make this functionality available als quick as possible we didn’t yet pre-test all of our different content elements And functionalities. In first step we focused on simple page translations to support your urgent request best.

So please please sensitise your editors that there might be still so bugs or thinks we first need to learn about
when using DeepL Translations with our Zehnder Typo3 system.

As mentioned, I’ll create a new docu page in Sandbox along my own tests and list all information already shared now with you.

Translation time:

For big pages it could happen that they run into an so called “GateWay Timeout” which is displayed to the editor on the typo3 screen.
But in the backend the translation process is still running and processed up to 4 minutes.
So whenever you get an “GateWay Timeout”, please first check after about 4 minutes if all content items have been translated or not. Please only assign a SNOW ticket in case after about 4 minutes not all content items have been translated.