Bug 331760 - Reply malfunction: Incorrect text encoding when replying on messages with quoted-printable Content-Transfer-Encoding
Summary: Reply malfunction: Incorrect text encoding when replying on messages with quo...
Status: RESOLVED DUPLICATE of bug 298349
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.11.5
Platform: Debian unstable Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-05 11:19 UTC by borissh1983
Modified: 2015-08-31 10:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description borissh1983 2014-03-05 11:19:59 UTC
Someone is using a webmail to send an email with hebrew text in it, Choosing reply on the received email all hebrew text is incorrectly encoded in the reply message.


Reproducible: Always

Steps to Reproduce:
1.Send an email with Hebrew text in non utf-8 encoding (example via Gmai web interface)
2.Open the received email using Kontact validate that you can see the hebrew Correctly
3.right click on the message and choose reply
4. Check if text is shown correctly in the new window
Actual Results:  
in reply window the text is incorrectly encoded

Expected Results:  
reply window the text should be correctly encoded

If email is sent only with plain text and Content-Transfer-Encoding is base64  - reply works as expected :

MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"

15HXkNeSINee15XXlteoINeR16fXldeg15jXkNen15gsIArXntep16TXmCAyCtee16nXpNeYIDMK
15TXm9eV15wg15TXnNeaINec16TXlwo=

Bad example  (split): 
Content-Type: multipart/alternative; boundary=089e0122991a2a090404f3a4f828


--089e0122991a2a090404f3a4f828
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=E1=EC=E4 =E1=EC=E4 =E1=EC=E4=20
Comment 1 Sergio Martins 2015-08-31 10:23:27 UTC

*** This bug has been marked as a duplicate of bug 298349 ***