Why do these little padlock icons appear in converted translation memory TUs?

Question

Hi all, I use Studio 2015 with SGML documents, and I'm running into a weird problem where the SGML tagging gets messed up somewhere along the line. Below is an image that shows the problem. Notice that the figure references are supposed to have INTXREF tags with the word Figure/Figura and then XREF tags whose attributes point to the actual figure element. That's how they were saved, but somehow the tagging goes awry and the word Figura (only in the target, mind) ends up inside the XREF tags, and I get these little padlock icons to boot. I suspect that this happens during a TM conversion process (I think a contractor was using Studio 2014 when he/she created these TUs, and we here were still on Studio 2011 at the time). Anyone have a clue what happened here, or how to keep it from happening during future TM conversions? 
 Any enlightenment whatsoever would be appreciated. 
 Thanks 
 Jos&eacute;

Paul · Answer

Hi José, 
 
Would you be able to give me a small test file I can use the reproduce this problem? I need to be able to save a segment no containing these tags and then see them in the TM. My initial reaction to seeing this is that the TU in the TM came from a different source, so I need to be able to show how this is not the case. 
 
If you can supply a small file for this please email it to me at pfilkin@sdl.com 
 
Thank you 
 
Paul

Paul · Answer

Hi Jos&eacute;, 
 ok - here's what I tried to do. 
 
 I created a Studio 2014 project and populated a TM with four segments 
 I took that TM and "converted" it for Studio 2011. To be honest I have no idea what this means so I just reindexed the TM in Studio 2011. perhaps you can explain what's involved in converting a 2014 SDLTM for 2011? 
 Then I opened the SGM file in 2015 and pretranslated it with the 2011 TM 
 
 This is what I got: 
 
 I don't really know why #55 is a 100% match and not a CM match, but apart from that the results are ok. I think it's clear the problem is the result of there being something in your TM that was translated either in something else, and maybe converted to an SDLTM, or the files were tranlsated under different circumstances with locked content maybe... I don't really know. But I do think this is related to what's in your TM rather than a problem with 2015. 
 At least that's what it looks like to me. Wonder if anyone else has any bright ideas? 
 Regards 
 Paul

Trados Studio > 1. Trados Studio

Why do these little padlock icons appear in converted translation memory TUs?