Translation Enhancements with Multi-Site Manager translation-enhancements
AEM’s robust translation framework allows AEM content to be seamlessly translated by supported Translation vendors.
Translation Enhancements in AEM 6.5
Transcript
Hey, everyone. In this video, we will discuss AEM 6.5 sites translation enhancements. Let’s get started. From the AEM homepage, navigate to projects. You might have seen or used Project Master creating translation projects in the previous versions of AEM. Let me give you a quick overview. Project Master acts as a blueprint for creating projects. For example, you can create a master translation project with a list of members in your organization and their roles. After creating the Project Master, you can then create multiple translation projects based on this Project Master and every project would share the team members and other attributes added to the Project Master. Project Master accelerates project creation and makes it easy to manage team members working on a project. This capability was introduced in AEM 6.3 and lets you create a translation project within the projects window. AEM 6.5 you can now create or update a translation project using the references side rail. Let me show you how to do this. We have a sample Project Master created for translation projects with team members and their roles. You can create a translation project based on this Project Master within the project window. But, let’s take a look at another option to create this translation project from the side rail. From the AEM homepage, let’s navigate to sites, we retail, United States, English, and then select the equipment page. Select the references panel for this page and then click on language copies option.
Click on the create and translate option which provides a uses selection window for languages, and Project Master. Select Spanish as the target language, and then click on the project type option. Don’t add the option to select the Project Master; it’s available only for create translation project option, as for thats for the create multi-language translation project.
Select the project type as create translation project, and continue. Now, let’s select the Project Master that we created, in the previous step, and provide a title for you translation project.
Click create to complete the project creation. Navigate back to the project window. You can notice our translation project listed here. Let’s open the project to view its properties. You can notice that the team members and their roles are inherited from the translation Project Master. A link pointing to the respective master is also available right above the member list. Option to add a new member to the project would be hidden for this translation project. If you need a team member for this project to be added, it needs to be performed at the Project Master level and all translation projects using the Project Master will inherit the changes. We were able to successfully create a translation project for a site page right from the reference side rail using the Project Master. This experience is also available for assets and experience fragment references side rail. Let’s open the translation project summary, and under advance field, you can notice that automatically approve translations, automatically promote translation launches, and delete launch after promotions are selected by default, thereby reducing the number of steps required to translate content. If your organization requires to promote launch translations and upload translations as an additional step, you can uncheck the options and save your changes. Let’s start this translation job and you can notice that translation jobs status change from draft to approve. If the automatically approve translation option was unchecked, the status will then change from draft to ready to review, upon starting the translation job. Some of the other translation enhancements includes the ability to export translation objects in the form of JSON. AEM 6.4 and earlier versions support xml and xlf formats for translation objects.
You can now configure the export format to JSON format under your system console and configuration manager. Look for translation platform configuration, and then you can select the export format as JSON. Another translation enhancement with AEM 6.5, let’s look at authors who do not have access to AEM to make updates to translated content. Address already enlisted back into AEM, directly in the translation memory within the translation management system and to update the translations in AEM by resending translation job from translation management system to AEM. AEM 6.5 introduces several translation enhancements, making it easier for content approvals, and content authors to translate content. It also adds the JSON export format for translation objects to integrate with third party translation systems.
AEM 6.5 translation enhancements includes:
Auto-approve translation jobs: The approval flag in the translation job is a binary property. It does not drive or integrate with out-of-the-box review and approval workflows. To keep the number of steps in a translation job minimal, It is by default set to “automatically approve” in Advanced Properties of a Translation Project. If your organization requires approval for a translation job, you can uncheck the “automatically approve” option in Advanced Properties of a Translation Project.
Automatically delete translation launches: Rather than manually deleting translation launches in Launches Admin after the fact, it is now possible to automatically delete translation launches after they were promoted.
Export Translation objects in JSON format: AEM 6.4 and earlier versions support XML and XLIFF formats of translations objects. You can now configure the export format to JSON format using your systems console Config Manager. Look for Translation Platform Configuration, and then you can select the export format as JSON.
Update translated AEM content in Translation Memory (TMS): local author who does not have access to AEM can make updates to translated content, that was already ingested back into AEM, directly in the TM (Translation Memory, in TMS), and to update the translations in AEM by resending translation job from TMS to AEM
Translation Enhancements in AEM 6.4
Transcript
With Adobe Experience Manager 6.4, we’ve improved the workflow around translating your content, to make it more efficient and easier to use. There are multiple ways to create a translation project. Let’s begin in projects and click the Create button to create a new project. After selecting Translation Project and giving it a name, we’ll move to the Advanced tab to select our language and translation provider. In this case, I’m using Microsoft’s. In previous versions of Adobe Experience Manager, you were limited to selecting a single target language. This was by design, as you typically have different teams, reviewing the different language translations. In AEM 6.4, you can now select multiple target languages. AEM will still create separate jobs, that can be managed and processed independently. But this new workflow, will significantly speed up the process of creating those tasks.
We can now add some content to be translated. In this case, I’ll select my English content from my web site, then choose to create a language copy.
You can see it’s picked up my pages, assets, and any content fragments, dictionaries and tags associated with my content. From here, we can start any of these jobs and even see the progress. This approach of creating multiple jobs under a single project, makes it easier for customers to manage the translation jobs. It’s actually a more efficient way for AEM to process jobs, as well, which requires fewer CPE resources. I’ve started in the project’s admin, but many customers will wanna create these translation jobs, directly from the site’s admin, which is also possible. So I’m going to delete this project and look at the same workflow directly from sites. I’ll navigate to sites, then select my English content under Language Masters. From here, I’ll open up the side rail and choose REFERENCES and then LANGUAGE COPIES. As you can see, we’ve already created the structure for the German, French, Spanish and Italian languages. So when I click language copies, I’m given the option to update them. Clicking on Update language copies, brings up the capability to create a project and in AEM 6.4, I can create a multi-language translation project. I’m gonna select this and then give it a title. Clicking Update will automatically create a project similar to the one that we created via the project’s admin. Let’s navigate to the project’s admin now and take a look at it. I can see the new project and it may take a few minutes to fully create this project, depending on how many languages and how much content is involved. But when you refresh your browser, you’ll eventually see that it’s complete. The project card now also shows you how many translation jobs you have, as well as their status.
Clicking into one of the translation jobs, will show me the details. I can choose to start any of these jobs independently, or click on my project card to run everything. After a few minutes, the translation effort will be complete and the content will be ready to review. Let’s navigate back to sites and look at our language copies again.
We can now see, that the languages are ready for review. We can compare the language copy to the master or choose to promote the launch. Let’s promote the full launch, by selecting that option, then promoting the new and changed pages.
In AEM 6.4, we’ve also added a property that you can choose to display as part of your list view, to show the translation status of your pages. Let’s choose the list view and then click on view settings and add the new translated column.
We can see the status is now showing up and see these pages have all been translated. I’ve been clicking around a lot to launch these translation jobs, but we’ve also added a new feature in AEM 6.4 that will make this easier, as well. If we go back and look at the project properties, you’ll see a new option to automatically promote the launch after the translation. In fact, if you and your organization aren’t really using the launch feature, you can also automatically delete the launch, making the process incredibly seamless. This is especially true, when used alongside with the ability to schedule translations. I can select a value from this dropdown list to repeat the translation project daily, weekly, monthly, or yearly, then specify the details. For example, I want this to run every Monday at 2 A.M. This will automatically execute every job that is in a draft state. That’s a quick look at the new translation features in AEM 6.4. Thanks for your time.
Authors can now quickly and easily create multi-language translation projects directly from either the Sites admin or the Projects admin, set up those projects to automatically promote launches, and even set schedules for automation.
Additional Resources additional-resources
recommendation-more-help
bb44cebf-d964-4e3c-b64e-ce882243fe4d