How to avoid translating metadata? (converted an XML file to Word)

Question

Hi everyone, 
 I'm working with an XML file where I need to export it to bilingual word so it can be translated concurrently between 2 translators. This is required as my client doesn't own Trados and would like to comment in Word. So once everything is finalized, we can simply accept all changes and convert it to XML again for delivery. The client will then upload the file to their Design platform called Xyleme for further processing and output. 
 Before project start, they requested us to provide a mock XML with pseudo translation for testing. So I used the pseudo translation function in Trados to do auto text filling, and returned the mock XML. However, they told me that the instructional metadata has been tempered (probably caused by pseudo translation) and suggested me to change the parser setting. I have no idea what and where it is. Is this a setting I can apply during the XML to Word conversion? or how can I avoid translating the metadata by accident? I assume Trados is smart enough to leave out the metadata but seems like it's not. Hope someone can shed some light and thanks in advance! 
 Best Regards, 
 L

Paul · Accepted Answer

Louis Ng 
 Louis Ng said: I assume Trados is smart enough to leave out the metadata but seems like it's not. 
 Trados is only as smart as its user... so you need to customse the parser rules accordingly. XML is very flexible and Trados provide you with the tools to do this. I suggest you start here: 
 https://multifarious.filkin.com/2014/06/01/custom-xml/ 
 And if you still need help you will have to share the xml file, or part of it, for anyone to be able to help you.

Paul · Answer

Louis Ng 
 Louis Ng said: I couldn't share the XML on the forum as I've signed NDA.. but if anyone is kind enough to look into this with me, I may can share part of it in a secure way. 
 All you need to do is pseudo-translate the XML ad save the target. Once you have done this surely you can anonymise anything left in the header that you think is important to hide and share that? 
 Louis Ng said: For example, will I be able to tell from the converted Word file which are instructional metadata so that i can leave it in it's original form? 
 Frankly this is a ridiculous way to work. If you need to handle XML for a customer then you should learn how to do it properly. It's probably not difficult and if you were to take the time to prepare a sample of the structure we could help you. We're not interested in the translatable content at all... only the structure of the file.

Paul · Answer

Louis Ng 
 ok - we're getting closer. That table seems to be in here for example: 
 
 Note that the translatable text is inside the text attribute of the BoundedText element. Currently you have excluded this element and have no rule for the attribute: 
 
 So I changed it as follows: 
 
 In the rule it's this: 
 
 This will also pick up this for example... there are more: 
 
 Presumably this should also be translated? 
 Hopefully this will help you understand the difference between elements and attributes at least, so you can probably fix anything else like this.

Paul · Answer

Louis Ng 
 You have not applied the rule, you simply made the BoundedText translatable. I told you to do this: 
 
 This is what you did: 
 
 You have not extracted the attribute at all. Here's what you need to do: 
 
 Note: I made a small error in describing why you should name the filetype. You also need to name the File type identifier which you can't change now... you need to do this when you create the filetype in the first place. If you start to work with XML more you'll be glad you have the ability to do this because it can be very confusing when you can't tell one filetype from another.

Paul · Answer

Louis Ng 
 Louis Ng said: My translator followed your steps to change the attribute but it didn't work; we couldn't find the bounded text in our exported file or on Trados. I've helped him to check the filter and it's showing as boundedtext/@text so I trusted that he did it right this time. 
 Your settings file looks fine. Did you recreate the project with this new settings file? Maybe you simply changed the settings file in the existing project, and in this case you're wasting your time as the project has already been created with the old one. 
 Louis Ng said: My translator also gave me the list of filters that we have turned into untranslatable before we try the boundedtext. Not sure if it matters: 
 I suggest you speak to someone like Jerzy Czopik who "might" be happy to agree a fair price with you to produce the filetype you are looking for. I have the impression that you are using a very inexperienced Trados user, and certainly one who doesn't understand enough about how to work with XML to tackle your project professionally. You would save yourself a lot of problems if you hire the right resource to help you.

Trados Studio > 1. Trados Studio

How to avoid translating metadata? (converted an XML file to Word)

Top Replies