Closed Bug 1314910 Opened 8 years ago Closed 8 years ago

Reply to a mail with UTF-16LE encoded .tmx (XML) attachment uses UFT-16LE in the reply

Categories

(Thunderbird :: Message Compose Window, defect, P1)

45 Branch
x86
Windows 7
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1026989

People

(Reporter: szelenyit, Unassigned)

Details

Attachments

(1 file)

83.71 KB, application/x-zip-compressed
Details
Attached file bug.zip
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 :)
OS: Unspecified → Windows 7
Priority: -- → P1
Hardware: Unspecified → x86
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.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(mkmelin+mozilla)
Summary: reply to a mail with .tmx attachment → Reply to a mail with UTF-16LE encoded .tmx (XML) attachment uses UFT-16LE in the reply
That's been reported already (before my time).
Status: NEW → RESOLVED
Closed: 8 years ago
Component: FileLink → Message Compose Window
Flags: needinfo?(mkmelin+mozilla)
Resolution: --- → DUPLICATE
> 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.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: