Yes, unfortunately this seems to be a bug. Thank you for posting, I have had the same problem some days ago, but no time to post. So I can confirm & and maybe some other signs (I think diacritics they were and maybe also =) do cause problems. And this is new since SP2.

Best regards, Jerzy

What should we do? Ideas are welcome... :-) Our Project Managers simply don't have time to check if every .sdlxliff file in a big project will open correctly... In stead, we have to wait for vendors to get back to us when they open the packages and start working... Then I have to fix the xml issue in the .sdlxliff and create a new package for the vendor facing the problem...

What should we do? Ideas are welcome... :-) Our Project Managers simply don't have time to check if every .sdlxliff file in a big project will open correctly... In stead, we have to wait for vendors to get back to us when they open the packages and start working... Then I have to fix the xml issue in the .sdlxliff and create a new package for the vendor facing the problem...

Hi Torben,

Perhaps you can check the SDLTMs beforehand and then export the TM as a TMX.  Then search replace the ampersands and  recreate the TM.  I know this is a pain, but at least it's something you could do to ensure things work when you do send the packages out.  So don't create packages with TMs that contain this problem.

It has been handed to development who will work on a fix.