Trados Live Essential/Live Team/Enterprise
Trados Business Manager
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Ideas Community
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Live Team Ideas
Trados Live Essential Ideas
Trados Live Terminology Ideas
Trados Enterprise Ideas
Trados Online Editor Ideas
Trados Business Manager Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
The Multilingual XML Filetype is a new filetype available for Trados Studio SR2 and later. The basic usecases for this filetype are:
The filetype was also presented at the Autumn 2021 Elevate conference:
The filetype can be installed through the AppStore integration in Trados Studio (image below), or by downloading the sdlplugin file from the website and double clicking it to invoke the plugin manager.
Once installed you should find the new filetype installed here:
If you don't see the filetype in your options make sure you have enabled it here:
You will also find two new batch tasks:
These will be explained below.
It's very important to make sure that the paths are correct. The main reason for the filetype not being associated with the file opened for translation is failing to accurately specify the XPath locations. If you have any questions on how to do this for your filetype the recommendation is to ask for help in the appropriate forum
Regex and XPath
XML files come in all shapes and sizes so some knowledge of how to use XPath is essential. If you are completely new to XPath you may also find these resources useful:
The last two at least relate to using Trados Studio.
A last point on this section. If you wish to add a new language into the file that wasn't present in the source then this is also possible. Just add the new language to your language settings for the project and then create the appropriate rule in the language mappings. You can now translate this additional language and when you save your Multilingual Translations via the batch task you will find the new language has been added to the file based on the XPath expression you used to map this additional language.
This section is the same as for any embedded content processing in Trados Studio. An important point is that you do not have this ability to use another filetype (html for example) as an embedded content processor in the XLIFF filetypes supported by Trados Studio. So this is a big advantage, especially when handling XLIFF files that make heavy use of large CDATA sections in single translation units.
This section supports the ability to "tag" text as a placeholder in Trados Studio irrespective of whether you are also using an embedded content processor or not. This is an extremely useful feature because all other filetypes in Trados Studio that offer embedded content processing are either one or the other, so regex rules for everything OR use another fietype like html for the embedded content processing.
The filetype comes with four predefined rules that you can use if appropriate, or remove and just create your own rules. The process is simple, just click on Add:
Then write your regular expression, define the segmentation hint, and if you wish you can add a description. It's worth adding a description because you can also import/export the rules you have created to make it easier to share with others, or even maintain a library for yourself that you can simply import and then remove the ones you don't need as a starting point when setting up your filetype for a specific project. The different options available to you are defined across the toolbar:
This section provides entity support that works the same way as it does for any filetype in Trados Studio that supports them. See the producthelp for more details.
This section provides support for QuickInserts that works the same way as it does for any filetype in Trados Studio that supports them. See the producthelp for more details.
When you add a multilingual XML file, properly set up, your multilingual project will be created for all the language pairs specified allowing you to manage the project in the usual way.
In the Installation section above it was mentioned that two new batch tasks are added to Trados Studio:
Import Multilingual Translations
This batch task will import all translations that may be present in the source file. If you have the Professional version of Trados Studio you can create custom tasks that include this task as part of the project preparation. In the screenshot below you can see the task is a custom task that only does three things - converts to translatable format, copies to target languages and imports the multilingual translations:
If you are using the Freelance version of Trados Studio then you will need to run this task after the project has been created.
The options allow you to do four things:
Generate Multilingual Translations
This batch task will generate the target multilingual file when you have completed the project (or earlier if you wish). It is different to the out of the box generate target translations, which will also work, because it will take the target translations from each of the files you have translated in a multilingual project and merge them back into single files again. This will be very beneficial because the out of the box task will create separate files for each language pair being translated and you would then have to merge them all into single files manually afterwards.