Anders Larsson 

You are using a customized XML file type I guess? It's up to how you set up the parser which fields are exposed to the translator. Could you post a screenshot of how your parser is set up?

Daniel

It uses XML 2: Any XML, and the parsing is automated there, there aren't any settings. 

Anders Larsson 

Okay, I understand. Yes, just using this out-of-the box file type will expose every element content. You need to create a custom file type for almost every XML file. That is inevitable because XML is an extremely versatile file format and there is no way Studio could know what you want to translate and what not. What you posted above looks very simple – do you know how to set up a custom file type or would you appreciate some help? (I found this kind of thing daunting when I first started, happy to lend a hand, esp. if the file is really that simple…)

Hi Daniel,

I haven't done anything like this for a very long time, so a helping hand would be very much appreciated. :-)

Anders Larsson 

Can you post your file here or send it to me?

Sorry, but it's highly classified. I will try to customize the file type myself, just need a few pointers in the right direction I think.

Anders Larsson 

I understand about not sharing the file. An XML file needs a root element, however it's called. I called mine “root” in the below example. The structure is important.

In the parser, you describe the location of the translatable text to Trados Studio using a language called XPath. That's all total standard.

Your example was a bit incomplete, so I completed it, and it looks like this:

You want to tell Studio: Translate all content of all “para” elements, if they are descendents of a “loc” element where the attribute “language” has the value “sv-SE”.

In this case, it's this:

/root/loc[@language="sv-SE"]/note/para

(The code module has “CoffeeScript” but it does not have XPath!!)

In Studio, you select File Types in “Project Settings” and then “New”. Base your file type on XML 2.

In one of the following screens, select “XPath rules”, not “Element rules”.

Forward to the "Parser" screen, then enter a catch-all for what you don't want to translate:

Then enter your XPath expression of what you DO want to translate:

Finish and try to preview your file, it should look like this:

If your root node is different you have to adjust accordingly.

Hope this helps

Daniel

PS Good read: https://multifarious.filkin.com/2014/06/01/custom-xml/ and lots more blog posts on XML filetypes on that website.

Wow, super thanks for the detailed description, Daniel! I must confess that I still haven't gotten it to work though. My client is ok to post-edit the target files though, so I will take another look at this later. Once again, big thanks for taking the time.

/Anders  

Anders Larsson 

Okay, not sure where you're stuck. You can try

//loc[@language="sv-SE"]/note/para

instead, that is a bit less specific and might work as-is.

Anders Larsson 

Okay, not sure where you're stuck. You can try

//loc[@language="sv-SE"]/note/para

instead, that is a bit less specific and might work as-is.