Romain Neveu 

Oh no! I see the problem but we dont have a TM tag mapping to help address scenario's like this.
Would be a good app - which I have noted so watch this space.

What you can do is change the TM penalties to 0, which will give you 100% match



But you will still have to move over the source tags to target tags, so while your analysis will be correct your effort will not be saved.

Depending how big your TM is and depending how big a project this is, I would be tempted to see if you can export your TM to TMX.
Goal would be to amend how the TM data is being displayed, to update new TM that has correct/improved tag formatting.
You would need to download the TMX file type from the private app store as well as Data Protection Suite 

I dont have your files, so here is a bit of an experiment based on my files.

See TM content with <> raw tags. Export as TMX
 
See TMX file in Editor View, using TMX file Type

I created a rule using Data Projection Suite, stating that content between <> should be tagged

Once complete, I then have this

By no means is my example perfect as my regex rule was too inclusive and some actual translated content got tagged.
Mostly likely I would need to specify each <tag name> individually to get a more accurate results.
But conceptually I hope it gives you an idea of how TMX with Data Projection Suite can be used to review your "*.sdlTM" data

Then you would updated to a new TM and hopefully achieve not only better analysis results but also reduced tagging effort. 

I hope this gives you something to explore if you feel it necessary
Have a good day

Lyds 

 Romain Neveu 

Oh no! I see the problem but we dont have a TM tag mapping to help address scenario's like this.
Would be a good app - which I have noted so watch this space.

What you can do is change the TM penalties to 0, which will give you 100% match



But you will still have to move over the source tags to target tags, so while your analysis will be correct your effort will not be saved.

Depending how big your TM is and depending how big a project this is, I would be tempted to see if you can export your TM to TMX.
Goal would be to amend how the TM data is being displayed, to update new TM that has correct/improved tag formatting.
You would need to download the TMX file type from the private app store as well as Data Protection Suite 

I dont have your files, so here is a bit of an experiment based on my files.

See TM content with <> raw tags. Export as TMX
 
See TMX file in Editor View, using TMX file Type

I created a rule using Data Projection Suite, stating that content between <> should be tagged

Once complete, I then have this

By no means is my example perfect as my regex rule was too inclusive and some actual translated content got tagged.
Mostly likely I would need to specify each <tag name> individually to get a more accurate results.
But conceptually I hope it gives you an idea of how TMX with Data Projection Suite can be used to review your "*.sdlTM" data

Then you would updated to a new TM and hopefully achieve not only better analysis results but also reduced tagging effort. 

I hope this gives you something to explore if you feel it necessary
Have a good day

Lyds 

Thank you very much for your time and for explaining this procedure Lydia, I will try and implement this on my TM.

Have a great day too!

Romain Neveu you are welcome