"Probability score": 0.8

"Question improvement suggestion": Please provide the version of Trados Studio you are using and any steps you have already taken to try and solve this issue.

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

Hello,

To translate only segments with a translate="yes" attribute in your DITA files in Trados Studio, you can use a similar approach to the one you mentioned for 'astX:md=true' attribute. Here are the steps:

Step 1: Open your Trados Studio and go to the "File Types" settings.

Step 2: Find and select the DITA file type.

Step 3: Go to the "Parser Rules" section.

Step 4: Add a new parser rule. Set it as always translatable and use the XPath expression '//*[@translate='yes']' to extract text from any element with the 'translate=yes' attribute.

Step 5: Add a second rule to not extract anything at all, using the XPath expression '//*'. This ensures that only the first rule is applied.

Step 6: Disable all other rules to maintain a clean sheet for these settings.

Please remember to save your changes and apply these settings to your project. This should allow you to translate only the segments with a translate="yes" attribute in your DITA files.

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

Thank you for your approach,

Unfortunately, adding the XPath expression '//*' breaks the entire document. Nothing else is displayed for translation, the file to be translated is empty.

Here below are the settings as you suggested:

Leylak de Caupenne 

Try switching the order of your rules.  You excluded everything with your first rule so there is nothing left to parse.

Dear Paul,

Thanks a lot for your reply.

I had to adjust some tags that are inbetween tags, but I confirm your solution worked!

Hello Paul, we've been facing another issue with the filter. This time, our client placed the "translate = yes" at the level of topic. However, even though we placed //topic below or above "translate = yes", it did not identify what needed to be translated. The file counted 0 words.

Here is the example of file:

We are trying to work like this as some of the client's file do not have "translate = yes" attributes and need to be translated integrally but we do not want to create two different Studio project (at the moment we create one project for the files without any attribute, and one project with the filter. If we place the files without the attributes, they do not show any words due to filter.

Please let me know if you need more details and more examples.

Thanks in advance for your help.

Hello Paul, we've been facing another issue with the filter. This time, our client placed the "translate = yes" at the level of topic. However, even though we placed //topic below or above "translate = yes", it did not identify what needed to be translated. The file counted 0 words.

Here is the example of file:

We are trying to work like this as some of the client's file do not have "translate = yes" attributes and need to be translated integrally but we do not want to create two different Studio project (at the moment we create one project for the files without any attribute, and one project with the filter. If we place the files without the attributes, they do not show any words due to filter.

Please let me know if you need more details and more examples.

Thanks in advance for your help.