User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20161031133903 Steps to reproduce: 1. Write an email with a .tmx attachment (see first attachment in the zip below: this file is a memoq cat-tool's file, formerly an .xml file with .tmx extension). 2. Receive the mail. 3. Open the mail. 4. Write a REPLY mail with some body text (and with NO attachment) 5. Send the mail. Actual results: In the sent mails folder, you will see the message, but the body disappear completely, and you'll see just one single sign (see second attachment in the zip below) Expected results: I want to see the whole message in the body :)

Yes, I can confirm this. The problem is that the UTF-16LE encoding is taken from your pseudo XML file and used in the reply. As a workaround, you can simply switch the encoding to Unicode or Western and there is no problem. In the meantime let me find out what the status of UTF-16 encoding is in TB, Magnus, do you know. UFT-7 is discontinued, right, but I've never seen UTF-16 being used other than internally.

That's been reported already (before my time).

> In the meantime let me find out what the status of UTF-16 encoding is in TB, > Magnus, do you know. UFT-7 is discontinued, right, but I've never seen > UTF-16 being used other than internally. I don't know, why CAT-tools (like MemoQ or Trados) uses UTF-16 instead of UTF-8. (The tmx specification allows utf-8 too: goo.gl/H2Bjs5 ) Thanks for the info though.

Since I made this a duplicate, my NI got lost. I'll ask again in the other bug 1026989.

Watch bug 961983. There we will put a stop to UTF-16 for composition.