Open Bug 532367 Opened 15 years ago Updated 8 years ago

Incorrect encoding with mail.strictly_mime (lost spaces)

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

People

(Reporter: vanav, Unassigned)

Details

(Keywords: testcase)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729) Build Identifier: Thunderbird/3.0 - Build ID: 20091130201643 If mail.strictly_mime is true, and using non-English characters, mail body is encoded in quoted-printable. After decoding, spaces between some words are lost. Reproducible on editing draft message, forward, edit as new etc. Reproducible: Always Steps to Reproduce: 1. Create new message with body: "раз два три четыре пять шесть семь восемь девять десять" (possible any non-English characters, without quotes). 2. Save as draft. 3. Edit. You'll see: Actual Results: "раз два три четыре пять шестьсемь восемь девять десять" - space between 6th and 7th words is lost. Expected Results: "раз два три четыре пять шесть семь восемь девять десять" Message source: =D1=80=D0=B0=D0=B7 =D0=B4=D0=B2=D0=B0 =D1=82=D1=80=D0=B8 =D1=87=D0=B5=D1=82= =D1=8B=D1=80=D0=B5 =D0=BF=D1=8F=D1=82=D1=8C =D1=88=D0=B5=D1=81=D1=82=D1=8C= =D1=81=D0=B5=D0=BC=D1=8C =D0=B2=D0=BE=D1=81=D0=B5=D0=BC=D1=8C =D0=B4=D0=B5= =D0=B2=D1=8F=D1=82=D1=8C =D0=B4=D0=B5=D1=81=D1=8F=D1=82=D1=8C ^ seems space 2 lines above here makes troubles.
May be related to bug 307023.
Component: General → Message Compose Window
QA Contact: general → message-compose
I can confirm this issue with this STRs: 1. set mail.strictly_mime = true 2. select an HTML account; 3. create a new message with this body раз два три четыре пять шесть семь восемь девять десять 4. save message as draft 5. edit draft then observe behavior descrived in comment #0 It's an editor problem? Mozilla/5.0 (Windows NT 6.1; rv:2.0b9pre) Gecko/20110108 Thunderbird/3.3a2pre
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
(In reply to comment #2) > It's an editor problem? Doesn't look like it, but can't tell for sure without debugging.
You need to log in before you can comment on or make changes to this bug.