Problem

Phrase uses a non-xliff compliant syntax for their visual markup in their xliff that is not even a tag. Therefore in translate5 it is simply shown as text inside the segment.

Syntax looks like this:

Unable to render embedded object: File (AMDAwAAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==) not found. And this is not bold.

Yet it should be protected as internal tags.

Solution

Change our import parser so that this markup in mxliff documents is converted to internal tags in translate5.

The import parser should only work that way, if the file format mxliff is detected. This means, if there is a namespace in the header defined, that contains the word "memsource" or "phrase". So something like this:

xmlns:m="http://www.memsource.com/mxlf/2.0"

Change the export so that the tags are  converted back to their mark-up.

See linked TS task for example file and screenshots how this looks in phrase.