Hi Just wanted to share the solution we looked at for this particular problem. 

1. First of all, the xlf file provided had no target elements at all in it.  We needed a target in there so we could create an xml filetype handling embedded content and just translate the target.
2. So, we did this with a decent text editor that supports Regex.  Search for this:
   (<trans-unit id=".*?"><source>)(.*?)(</source>)(</trans-unit>)
   And replace with this:
   $1$2$3<target>$2</target>$4
3. This gave us an xlf file that now contains target elements and they all contain a copy of the source
4. We could then create a new xml filetype that extracted text from the target element, and we added an embedded content filter using the html filetype

Now the file could be opened and all the tagged text was protected.

Regards

Paul

Hi Paul,

I had used this exact method on a different xliff file type and it had saved my life.  This reminded me the inability to use embedded content processors for all kinds of file types in Studio. If am not wrong, embedded content processors can be only used for xml file types. This might be logical but there is one feature in Memoq that I want to see in Studio too. It is called regex tagger. Sometimes we receive an sdlxliff file containing too many unprotected tags. I think it would be great for us if Studio can also offer us an option to protect certain words or characters as tags for each kind of filetypes. What do you think?

Please let me know if you think this should be discussed in a separate topic.