This Mover Tip will show you how you can translate Digital Articles from one language to another using either the AWS or Google Translate Tasks. Smart Mover version 10.1.0 will be required since that is the first version that includes those Tasks.
The general flow is that once the Article is finished in the first language the Mover Process downloads the native Article file, translates it (into one or more languages) and then places the translated variation(s) back in the same Dossier as the original… maintaining all the image links from the original. Once this is done then those language variations can be published into the appropriate channels.
But before we start there are a few important issue to consider:
1. You will need either a AWS or Google account. Depending on your monthly usage there can be charges for their service. See the Smart Mover User Guide for more information.
2. Both AWS and Google Translate use machine learning tools to perform this service. They do not just translate each word individually. Instead they operate on entire sentence or paragraphs. This is done to make sure that the context of each word is properly applied. For example, in English, the word “bat” has 2 entirely different meanings. One you use to play baseball or cricket the other is a small flying mammal. If you do not look at the entire sentence then individual words could be translated incorrectly. But this presents a problem when translating sentences that include multiple styles. In order to maintain that styling, those styled words need to be translated individually which then may result in an incorrect result. Additionally, some languages have different sentence structures and individual words might not have a single corresponding word in the new language. So it is best to apply word or groups of words styling after translation is complete. This may seem like a burden but please consider the next item below.
3. These translation tools are not perfect! You will need to review the end result before any kind of publication… which is also a good time to apply any individual word styles that you may require.
So onto the Smart Mover Process:
1. Enterprise Download: Build a query that selects the Digital Articles you want to translate…. probably based on Status... for instance “Ready for Translation”. Include just the Native file and the “MetaData” file. I set my Destination to a folder I called “In”. You will probably also want to “Set Status to Next” so that the same files do not get reTranslated over and over.
2. XSL Transform: We are going to convert the MetaData file(s) downloaded in Step 1 into “-metadata.xml override" files which we will later use to upload the translated articles. This is how we make sure the translated file is placed in the same Dossier as the original and that the image links are properly set.
Set the Source folder to the “In” folder from Step 1. Using the XSL file found here.
Set the Destination to a folder appropriately named for the language you want to translate to. In my case I used “Spanish”.
Repeat this Task for each language you want the Article to translated into… with each obviously going into a different appropriately named Destination folder.
On only the last XSL Transform also make sure you select the "Delete Original" option.
3. AWS or Google Translate: Create one of these Tasks for each language you decide to use in Step 2 above.
You can probably use either service. (I will post another message on this forum about the pros and cons of each). Set the Source to “In” folder set in Step 1 above, and the Destination to the appropriate same Destination folder(s) you used in Step 2.
Set the Source and Destination Language popups appropriately. For Google you will need to hit the Get Languages button to populate the popups with their list of currently supported languages. “Include Digital” which will disable the “Auto” language detection feature of the Task. Select an appropriate “Cannot be Translated” folder… which will probably go unused since the “Auto” feature is turned off… although there are still some reasons that some files might not be able to be translated.
On only the last Translate Task select the “Delete Original” option to clean up the “In” folder and make sure these file do not get processed again.
4. Rename Files: We need to rename the Articles so that once they are placed in the Dossier we can easily tell which one is which language… and we do not want duplicate named Articles in the same Dossier. So for each language folder created in Step 2 create one of these Tasks.
Set the Source folder to one of the language folders and do something like the following:
… where in the “To” change “ES” to something that designates the appropriate language. In this case I just used “ES” the widely accepted code for Spanish.
5. Rename Files; We also need to rename the -metadata.xml file exactly like we did with the Article files.
So for each language folder also do something like:
.. again where “ES” in the “To" is the same as in Step 4.
6. Enterprise Upload: We are now ready to upload the translated files and we need to create an Enterprise Upload Task for each language.
Set the Source folder to the language folder defined in Step 2 above, Delete Original and set the Brand and other parameters.
Once this Process completes in each Dossier that included one of the Articles downloaded in Step 1 you will find the the translated varitations. The following screen Content Station Dossier screen shot shows my results. Before I ran this Mover Process the only Article was “The Fresh Chef Digital”… after it also contains Articles “ES” (Spanish) and the “zh” (Chinese) variations