One of our clients sent us a XML file from the cms Tridion. Is there a way to translate these files and handle the tags and embedded content properly without having to come up with regex ourselves?
Please see a screenshot below of what part of the text looks like right now in SDL Studio 2019.
I can't get your screenshot to display bigger than thumbnail size.
Daniel
Hi Daniel, thanks. I will add a better screenshot soon.
I am just a bit puzzled why the files are appearing with all the embedded content visible. Tridion seems to be SDL software and I would expect the files to be easier to handle. Maybe I am missing something.
There are many possibilities to customize how xml files are read by Studio, it's widely used format. There are standard methods to deal with embedded content etc.
If you can post a snippet of the file here then people will find it easier to help. Please post text, not a screenshot...
Daniel
There are many possibilities to customize how xml files are read by Studio, it's widely used format. There are standard methods to deal with embedded content etc.
If you can post a snippet of the file here then people will find it easier to help. Please post text, not a screenshot...
Daniel
Thank you for your reply Daniel. I opened the file in Notepad++ and copy/pasted some text below.
We have handled xml files for clients before and we have used custom xml file types and (with help) used regular expressions but maybe someone has already figured out a way to handle xml files from Tridion in Studio?
<Component tcm-id="tcm:837-164159" LastModifiedDate="2018-07-19T16:26:34" title="Vence - 01 - X - Key activities - List">
<title>Key activities : developping customized control solution and smart services for HVAC systems &amp; plant room</title>
<menuitems>tcm:837-164157</menuitems>
<menuitems>tcm:837-164158</menuitems>
<menuitems>tcm:837-164174</menuitems>
<menuitems>tcm:837-164175</menuitems>
<relatedlinks>
<openinwhichwindow>NewWindow</openinwhichwindow>
</relatedlinks>
</Component>
</Schema>
<Schema tcm-id="tcm:837-102651-8">
<Component tcm-id="tcm:837-164177" LastModifiedDate="2018-07-17T13:36:57" title="Vence - 03 - Equipments/Countries/Electricity/Kwh">
<content> &lt;div style="width: 100%; background-color:white;"&gt;
&lt;div class="container container-theme container-theme-medium" style="overflow:hidden;text-align:center;"&gt;
&lt;div class="row" style="text-align:center;margin-top: 20px;"&gt;
&lt;div class="col-sm-3"&gt;
&lt;div style="background-color:#16468e;height: 120px; box-shadow: 0 0.1rem 0.3rem rgba(0, 24, 48, 0.2); display: flex; flex-direction: column; justify-content: center;"&gt;&lt;h3 class="heading-alt" style="margin: 0px;"&gt;&lt;span style="color:white;"&gt;+1 300&lt;/span&gt;&lt;/h3&gt;
&lt;h4 class="heading-alt" style="margin-top: 0px;"&gt;&lt;span style="color:white;"&gt;Connected equipments&lt;/h4&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div class="col-sm-3"&gt;
&lt;div style="background-color:#16468e;height: 120px;box-shadow: 0 0.1rem 0.3rem rgba(0, 24, 48, 0.2); display: flex; flex-direction: column; justify-content: center;"&gt;&lt;h3 class="heading-alt" style="margin: 0px;"&gt;&lt;span style="color:white;"&gt;+3 000&lt;/span&gt;&lt;/h3&gt;
&lt;h4 class="heading-alt" style="margin-top: 0px; "&gt;&lt;span style="color:white;"&gt;Customers&lt;/span&gt;&lt;/h4&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div class="col-sm-3"&gt;
&lt;div style="background-color:#16468e;height: 120px;box-shadow: 0 0.1rem 0.3rem rgba(0, 24, 48, 0.2);display: flex; flex-direction: column; justify-content: center;"&gt;&lt;h3 class="heading-alt" style="margin: 0px;"&gt;&lt;span style="color:white;"&gt;+500 MW&lt;/span&gt;&lt;/h3&gt;
&lt;h4 class="heading-alt" style="margin-top: 0px; "&gt;&lt;span style="color:white;"&gt;Electricity saved&lt;/span&gt;&lt;/h4&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div class="col-sm-3"&gt;
&lt;div style="background-color:#16468e;height: 120px;box-shadow: 0 0.1rem 0.3rem rgba(0, 24, 48, 0.2); display: flex; flex-direction: column; justify-content: center;"&gt;&lt;h3 class="heading-alt" style="margin: 0px;"&gt;&lt;span style="color:white;"&gt;+6 000 000 KWH&lt;/span&gt;&lt;/h3&gt;
&lt;h4 class="heading-alt" style="margin-top: 0px;"&gt;&lt;span style="color:white;"&gt;Daily transfer&lt;/h4&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p style="text-align: left;margin-top:20px;"&gt;&lt;em&gt;Source: Estimates based on existing TES solutions at customer sites&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;</content>
Hello Daniel, thank you for your reply. We have handled xml files from clients before using custom file types and (with help) regular expressions.
I was hoping there would be a standard way to handle xml files from Tridion or maybe a Community user has already figured out how to do it.
Please see below some text that I copy/pasted after opening the file in Notepad++.
<Component tcm-id="tcm:837-164159" LastModifiedDate="2018-07-19T16:26:34" title="Vence - 01 - X - Key activities - List">
<title>Key activities : developping customized control solution and smart services for HVAC systems &amp; plant room</title>
<menuitems>tcm:837-164157</menuitems>
<menuitems>tcm:837-164158</menuitems>
<menuitems>tcm:837-164174</menuitems>
<menuitems>tcm:837-164175</menuitems>
<relatedlinks>
<openinwhichwindow>NewWindow</openinwhichwindow>
</relatedlinks>
</Component>
</Schema>
<Schema tcm-id="tcm:837-102651-8">
<Component tcm-id="tcm:837-164177" LastModifiedDate="2018-07-17T13:36:57" title="Vence - 03 - Equipments/Countries/Electricity/Kwh">
<content> &lt;div style="width: 100%; background-color:white;"&gt;
&lt;div class="container container-theme container-theme-medium" style="overflow:hidden;text-align:center;"&gt;
&lt;div class="row" style="text-align:center;margin-top: 20px;"&gt;
&lt;div class="col-sm-3"&gt;
&lt;div style="background-color:#16468e;height: 120px; box-shadow: 0 0.1rem 0.3rem rgba(0, 24, 48, 0.2); display: flex; flex-direction: column; justify-content: center;"&gt;&lt;h3 class="heading-alt" style="margin: 0px;"&gt;&lt;span style="color:white;"&gt;+1 300&lt;/span&gt;&lt;/h3&gt;
&lt;h4 class="heading-alt" style="margin-top: 0px;"&gt;&lt;span style="color:white;"&gt;Connected equipments&lt;/h4&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div class="col-sm-3"&gt;
&lt;div style="background-color:#16468e;height: 120px;box-shadow: 0 0.1rem 0.3rem rgba(0, 24, 48, 0.2); display: flex; flex-direction: column; justify-content: center;"&gt;&lt;h3 class="heading-alt" style="margin: 0px;"&gt;&lt;span style="color:white;"&gt;+3 000&lt;/span&gt;&lt;/h3&gt;
&lt;h4 class="heading-alt" style="margin-top: 0px; "&gt;&lt;span style="color:white;"&gt;Customers&lt;/span&gt;&lt;/h4&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div class="col-sm-3"&gt;
&lt;div style="background-color:#16468e;height: 120px;box-shadow: 0 0.1rem 0.3rem rgba(0, 24, 48, 0.2);display: flex; flex-direction: column; justify-content: center;"&gt;&lt;h3 class="heading-alt" style="margin: 0px;"&gt;&lt;span style="color:white;"&gt;+500 MW&lt;/span&gt;&lt;/h3&gt;
&lt;h4 class="heading-alt" style="margin-top: 0px; "&gt;&lt;span style="color:white;"&gt;Electricity saved&lt;/span&gt;&lt;/h4&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div class="col-sm-3"&gt;
From what I can see you extract the <title> and <content> elements.
Most of the text you copied is HTML formatting, so you will have to use a custom XML file type with embedded HTML content processor.
You should not need to use any Regex here, just Xpath to describe what you want to translate, but really, you just need to know the name of the elements you want to use:
Daniel
We have handled xml files from clients before using custom file types and (with help) regular expressions.
That's incorrect way. XML files should NOT be handled as plain text! You should be handling XML files as XML, i.e. using custom XML file type.
See the Paul's article for a starter: multifarious.filkin.com/.../
Adding to what Evzen Polenka pointed out, XML is very flexible. That's both glory and misery - you will have to adapt your custom XML file type (surely with embedded HTML processor in your case) to suit your customer's implementation of their CMS. I never had anything to do with Tridion, but I am almost 100% certain that the localizable fields will vary from implementation to implementation and again within the CMS from item to item. Best would be if your customer could tell you what they want translated (Title, Content, Author, Metadata fields etc.)
It's a bit of a learing curve, but I found these tutorials easy to understand:
https://www.w3schools.com/xml/default.asp
https://www.w3schools.com/xml/xpath_intro.asp
Daniel
Thank you all. This is helpful!
I read that Tridion is a cms developed by SDL and that is why I was wondering if there would be a pre-defined file type to handle xml files from Tridion. We will look into the instructions for Xpath.
Tridion XML should be ITS (https://www.w3.org/International/its/ig/Overview) which means it should open automagically in Studio without you having to anything. But like anything the exports are probably customisable so if you need to do something to get at your translatable text it mimght be worth chatting to whoever prepared the files and sent them to you.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
As a follow-up for anyone who comes across this question, Tridion Sites is indeed an SDL, now RWS, offering. It integrates with the enterprise translation management systems from RWS including TMS, WorldServer, and Trados Enterprise.
There isn't a direct integration to Trados Studio, though CMS editors could send and re-upload source XML files as mentioned above.
Paul explained the expected format from Tridion Sites is ITS. This is the preferred approach and the ITS files are generated when using the Translation Manager feature in Tridion Sites to send CMS items to one of the above mentioned translation management systems. After jobs are received from the CMS to the translation system, linguists could work on the ITS files at the appropriate steps in the workflow (such as .For more information on Translation Manager, see the RWS Documentation Center topic.
Note that a Tridion Sites customer would need to first set up Translation Manager and a corresponding workflow in the TMS in order to send and receive translation jobs from the CMS.
Alvin Reyes | RWS
Twitter: @Nivlong | Personal Blog: CreateandBreak
Translate
