"Probability score": 0.8

"Question improvement suggestion": Please provide more details about the error message you are receiving, if any, and the steps you have taken to troubleshoot the issue. Also, it would be helpful if you could share the recent changes you made to your system or software.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello,

Based on your query, it seems you are trying to extract comments from a Multilingual XML file type in Trados Studio 2024 Professional. Here are the steps you can follow:

Step 1: Open your Multilingual XML file in Trados Studio.

Step 2: Navigate to the 'File Types' settings.

Step 3: Select the 'Multilingual XML' file type.

Step 4: In the 'Parser settings', you should see an option for 'CommentXpath'. This is where you can insert your XPath to extract comments.

Step 5: Enter your XPath in the 'CommentXpath' field. In your case, you can try using "langSet/descripGrp/descrip[@type='definition']".

Step 6: Save your settings and close the 'File Types' settings.

Step 7: Try running the 'Import Multilingual Translations' batch task again.

If you are still unable to extract comments, it might be due to the XPath you are using. Ensure that your XPath is correct and accurately points to the comments in your XML file.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

Neither the absolute, nor the relative XPath work in the CommenXPath field. Clearly, only the developers can answer whether this feature works, and, if yes, how

Yamagata Europe 

The answer is fairly simple because there is nowhere in the UI to use this.  The developer is on leave, but I suspect that this is there for a future initiative and is not a working part of the plugin yet.

Best to look at the UI rather than the underlying settings :-)

Yamagata Europe 

The answer is fairly simple because there is nowhere in the UI to use this.  The developer is on leave, but I suspect that this is there for a future initiative and is not a working part of the plugin yet.

Best to look at the UI rather than the underlying settings :-)