Changing translatability of an in-line element

Hi

Trados Studio 2021 SR2 - 16.2.12.9338

I have a MadCap Flare source file which uses the standard MadCap Trados parser.

Once loaded into a project, a translation is made:

Screenshot of a Trados Studio segment with HTML span tag, showing source and target text with 'Objects' highlighted in purple.

This translation is updated into the main TM.

Between this version and the next outsource, a decision is made to make the span class Value attribute not-translatable.

I add the a new rule to the MadCap Flare parsers:
Screenshot of Trados Studio parser rule settings with XPath for span class 'Value' set to not translate.

I now create a new project containing the original file, with the parser rule changes and same memory as before. The file in question has not changed, only my decision to treat that attribute differently.

After pre-translation, the segment is showing this in the editor.

Screenshot of a Trados Studio segment with HTML span tag, showing source text with 'Objects' highlighted in purple and a translation match at 90%.

The translation results window looks like this;

Screenshot of Trados Studio translation results window, showing a segment with mismatched HTML span tag highlighting in source and target.

This does not seem correct to me. I checked and the target side tagging is still present in the TM.

Maybe my expectations were too high but I was expecting to see this in the target side after translation: 
Maximum aantal rijen dat de <span class="Value">Objects</span> API kan ophalen

Has anyone else come across this type of situation before?

Is there a setting somewhere that will make it behave as I want?

Is there a workaround I can use?

Thanks

Mark



Generated Image Alt-Text
[edited by: RWS Community AI at 1:36 PM (GMT 0) on 10 Jan 2025]
emoji