Open Bug 598740 Opened 14 years ago Updated 2 years ago

In latest build mail in quoted-printable aren't well displayed (with html5.enable=true, with "Simple HTML", quoted-printable/base64 iso-8859-1 data is converted to utf-8, then Content-Type: charset=iso-8859-1 is applied to the converted utf-8 data)

Categories

(MailNews Core :: MIME, defect)

Product:
MailNews Core
Component:
MIME
Type:
defect

Tracking

(Not tracked)

People

(Reporter: stephane.gregoire, Unassigned)

References

Details

(Keywords: html5, Whiteboard: [View/Message Body As/Simple HTML case] [will_be_fixed_by_Bug 594646])

Attachments

(1 file)

Mail folder file, 6 mails
4.99 KB, text/plain
Details 
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100920 Firefox/4.0b7pre SeaMonkey/2.1b1pre
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100920 Firefox/4.0b7pre SeaMonkey/2.1b1pre

For example : "é" is shown as "é" and the source is : "=E9"

It's often happen in mail from yahoo or gmail.

Reproducible: Always




The build is from official build : seamonkey-2.1b1pre.fr.linux-i686.tar.bz2
Version: unspecified → Trunk
I've tried with en-US build Build identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100926 Firefox/4.0b7pre SeaMonkey/2.1b1pre and I've still have the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Test mail : attachment 479737 [details]
Mime-type of the attachment is "text/plain; charset=iso-8859-1" which
is set in Content-Type: header of the mail.
Stéphane Grégoire, view it by browser, with View Character Encoding=iso-8859-1
and utf-8. Mail data is written in utf-8, but "Content-Type:
charset=iso-8859-1" is set by mail sender or mail server, or mail server
transformed data to utf-8 from iso-8859-1 without altering iso-8859-1 in
Content-Type: to utf-8. It's malformed mail.

I looks that "Simple HTML" correctly handles "Content-Type:
charset=iso-8859-1", but "Original HTML" looks to fail to use iso-8859-1 and
looks to interpret it as utf-8.

"Interpretation as utf-8" is common phenomenon among this bug, bug 571704, and Bug 594646.
Setting dependency to bug 571704, for ease of tracking and search.

Stéphane Grégoire, can you check with html5.enable=false?
Status: RESOLVED → REOPENED
Depends on: 571704
Ever confirmed: true
Resolution: DUPLICATE → ---
Summary: In latest build mail in quoted-printable aren't well displayed → In latest build mail in quoted-printable aren't well displayed (malformed mail, mail data in utf-8 but Content-Type: charset=iso-8859-1, is shown as utf-8 by "Original HTML")
Component: MailNews: Message Display → MIME
OS: Linux → All
Product: SeaMonkey → MailNews Core
QA Contact: message-display → mime
Hardware: x86 → All
Summary: In latest build mail in quoted-printable aren't well displayed (malformed mail, mail data in utf-8 but Content-Type: charset=iso-8859-1, is shown as utf-8 by "Original HTML") → In latest build mail in quoted-printable aren't well displayed (with html5.enable=true, malformed mail, mail data in utf-8 but Content-Type: charset=iso-8859-1, is shown as utf-8 by "Original HTML". Content-Type: charset=iso-8859-1 is ignored)
With html5.enable=false on Seamonkey 2.1b1pre, Build identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100929 Firefox/4.0b7pre SeaMonkey/2.1b1pre.

It works with text/plain, simple html and original html!
I'm speaking of this message (I've only changed top level to .invalid with gedit 2.30) : https://bugzilla.mozilla.org/attachment.cgi?id=479737
(In reply to comment #5)
> It works with text/plain, simple html and original html!
(In reply to comment #6)
> I'm speaking of this message (I've only changed top level to .invalid with
> gedit 2.30) : https://bugzilla.mozilla.org/attachment.cgi?id=479737

Binary of attached mail is utf-8 as you can see by browser(see text/plain part data by browser). If attaced mail data is viewd by Tb 3.1/Sm 2.0 or Tb trunk/Sm trunk with html5.enable=false, I think View/Message Body As/Plain Text should show text/plain part in garbled like your screen shot of problem.

If binary of original mail is utf-8, trick may be next.
(1) Because multipart/alternative, "Text Plain" shows "data converted from HTML in text/html part to TEXT" instead of data in text/plain part.
(2) Because text/html part is quoted printable, and because quoted-printable data is correct iso-8859-1 data, "Plain Text" with html5.enable=false shows mail as expected.

What is binary of original mail?
You opened mail source as iso-8859-1 by text editor, text in text/plain part is shown as expected, modify top level, then you saved edited data in utf-8?
As mail data attached to Bug 600178 looks unmodified, I guess original data is utf-8 even though Content-Type: charset=iso-8859-X.
As I wrote bug 571704 comment #17, phenomenon at text/html part is same problem as bug 571704(i.e. same problem as Bug 594646).
Remaining issue in this bug(and duped Bug 600178) is utf-8 data in text/plain part even though Content-Type: ...; charset=iso-8859-1(or iso-8859-7).
If server side bug, data in text/html part was fortunately not altered by server because of quoted-printable data.
Woops. There is no <meta> tag in your test mail. i.e. your problem is different problem from bug 571704 and bug 594646.
Your case may be SeaMonkey specific problem.
Can you sort out phenomenon in SeaMonkey trunk/html5.enable=true on mail you attached?
1. View/Message Body As
   1-1. Original HTML
   1-2. Simple HTML
   1-3. Plain Text
Henri, looks like a bug in the HTML5 parser.
Status: REOPENED → NEW
Keywords: html5
(In reply to comment #5)
> With html5.enable=false on Seamonkey 2.1b1pre, Build identifier: Mozilla/5.0
> (X11; Linux i686; rv:2.0b7pre) Gecko/20100929 Firefox/4.0b7pre
> SeaMonkey/2.1b1pre.
> It works with text/plain, simple html and original html!

text/plain part in multipart/alternative is used as expected by "Plain Text" for your test mail. So, display by "Plain Text" has to be garbled characters with both html5.enable=false and html5.enable=true, because text/plain part is Content-Type: text/plain; charset=iso-8859-1 but data in the part is written in utf-8.
For "Simple HTML", Sm trunk's behavior seems different from Tb trunk. Garbled display was observed only by Sm's trunk in quick check.
Please sort out your check results.
  - Check with what software(Sm, Tb), with which build
  - Check with which mail
  - Check with which html5.enable value
  - Check with which View/Message Body As
(In reply to comment #10)
> looks like a bug in the HTML5 parser.

MIME code side fault instead of HTML5 parser is currently suspected. See bug 594646 comment #3 by Henri Sivonen, please.
And, this bug doesn't look same problem as bug 571704 and bug 594646, because of no <meta> tag in attached mail, utf-8 data in charset=iso-8859-1 part in attached mail, different display(one garbled, other not garbled) between Original HTML and Simple HTML by Sm, ....
(In addition to comment #12)
"é"(corresponds to =E9 of quoted-printable of iso-8859-1) written in utf-8 should be shown like "é" if Conten-Type: charset=iso-8859-1 is specified.
Bug 600178 is also report for SeaMonkey trunk. Chnaging back to Product=Seaonkey.
Component: MIME → MailNews: Message Display
Product: MailNews Core → SeaMonkey
QA Contact: mime → message-display
The utf-8 may be my fault, to get it I made Ctrl U, Ctrla A, and then Ctrl V in gedit then transform top levels to .invalid how can I make it?

Save mail but I have to edit mail to avoid more spams...

WADA, I can forward you the mail ; I'll do that now.
text/plain part under multipart/alternative mail you sent me;
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> e-mail programme
>
> =A0=A0=A0=A0
> =A0=A0=A0=A0
>
> Mercredi 29 septembre 2010
text/plain part is also quoted-printable. It's same as Bug 600178.

Why text/plain part of mail you uploaded was not quoted-printable and raw utf-8 binary is written?

Anyway, "Simple HTML" mode was different from "Original HTML" mode. And, quoted-printable or not looks affect only on "Simple HTML" mode. I attach test cases.
Subject: Case-XX-Y
 XX=01: multipart/alternative
 XX=02: multipart/mixed
 Y=A: <META content="text/html; charset=iso-8859-7" http-equiv=Content-Type>
 Y=B: <META http-equiv=Content-Type content="text/html; charset=iso-8859-7">
 Y=C: <META http-equiv=Content-Type content="text/html; charset=iso-8859-7">
View/Message Body As/Original HTML : Problem on Y=A only
View/Message Body As/Simple HTML   : Problem on any Y
I see :

This is a multi-part message in MIME format.

-------=ad4ec1ed327907cb8235665455ecff94
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

e-mail programme

    
    

Mercredi 29 septembre 2010

May a server transcoded it into quoted printable, I have often that at work...
I have tar.bz2 it so mail server will not transform it!

-- 
Sorry if I double post I had a server error!
Attachment #480044 - Attachment description: Mail folder file, 8 mails → Mail folder file, 6 mails
Correction.
 Y=C: No <META> tag
Attached non quoted-printable .eml data to your maii is detected as windows-1252 in my environment. You probably opened the .eml correctly as windows-1252 or iso-8859-1 by editor, and editor saved in utf-8 according to your default setting. If charset related issue, and if binary in data is important, modification of original data should be executed very carefully.
Problem of "Original HTML" is same as bug 571704 and bug 594646. But problem of "Simple HTML" looks relevant to quoted-printable, because problem occurs even on first text/plain part of multipart/mixed mail.
Keep this bug for diagnosis of "Simple HTML" and quoted-printable case.
Stéphane Grégoire, text/html part of your test mail corresponds to "Y=C: no <META>" of test mails I attached. So, if "Original HTML", garbled display with html5.enable=true doesn't occur as seen in bug 571704 and bug 594646.
Did you display the mail with "Simple HTML"?
Summary: In latest build mail in quoted-printable aren't well displayed (with html5.enable=true, malformed mail, mail data in utf-8 but Content-Type: charset=iso-8859-1, is shown as utf-8 by "Original HTML". Content-Type: charset=iso-8859-1 is ignored) → In latest build mail in quoted-printable aren't well displayed (with html5.enable=true, iso-8859-1 data is converted to utf-8, then Content-Type: charset=iso-8859-1 is applied to the converted utf-8 data)
If "Simple HTML", garbled display is shown even for next simple HTML of quoted-printable other than utf-8.
> Content-Type: text/html; charset=Shift_JIS
> Content-Transfer-Encoding: quoted-printable
> 
> <html><head></head>
> <body>
> <p>=93=FA=96{=8C=EA</p>
> </body></html>
Following is a part of your bug 571704 comment #9 on 2010-09-30.
> display in full html : correct
> display in simple html : wrong accents
I was confused when I wrote my commenr #3, by duping of this bug without diagnosis of your case and by utf-8 binary data of Content-Type: charset=iso-8859-1 part in mail data you attached...

Apparently your case is "Simple HTML" case.
1. You bug opener clearly say "display in simple html : wrong accents".
2. There is no <META> Tad in HTML of your case, so Bug 594646 can't happen in your case.
It's not SeaMonkey only issue. Changing to MailNew Core again.
Component: MailNews: Message Display → MIME
Product: SeaMonkey → MailNews Core
QA Contact: message-display → mime
Summary: In latest build mail in quoted-printable aren't well displayed (with html5.enable=true, iso-8859-1 data is converted to utf-8, then Content-Type: charset=iso-8859-1 is applied to the converted utf-8 data) → In latest build mail in quoted-printable aren't well displayed (with html5.enable=true, with "Simple HTML", quoted-printable iso-8859-1 data is converted to utf-8, then Content-Type: charset=iso-8859-1 is applied to the converted utf-8 data)
Whiteboard: [View/Message Body As/Simple HTML case]
Blocks: 571704
No longer depends on: 571704
FYI.
It was not quoted-printable only problem. If Simple HTML, problem was observed with base64 encoded simplest text/html mail other than utf-8 too.
Setting depenency to bug 594646 for ease of tracking and search.
Depends on: 594646
CC-ing to Zane U. Ji.
MIME issue? Mail display side("Message Body As" handling) issue?
Summary: In latest build mail in quoted-printable aren't well displayed (with html5.enable=true, with "Simple HTML", quoted-printable iso-8859-1 data is converted to utf-8, then Content-Type: charset=iso-8859-1 is applied to the converted utf-8 data) → In latest build mail in quoted-printable aren't well displayed (with html5.enable=true, with "Simple HTML", quoted-printable/base64 iso-8859-1 data is converted to utf-8, then Content-Type: charset=iso-8859-1 is applied to the converted utf-8 data)
No longer blocks: 593894
No longer blocks: 600178
Depends on: 572886
No longer depends on: 594646
Same bug here from a message by Windows Mail.

Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101111 Thunderbird/3.3a1pre ID:20101111031944
Same bug here in a message from gmail. Seamonkey 2.1b2pre 20101130 nightly build.

Content-Type: multipart/alternative; boundary=00151748db4c3bd83704965f70c5
--00151748db4c3bd83704965f70c5
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
--00151748db4c3bd83704965f70c5
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

No <meta> in the message source.

With html5.enable=true, garbled characters are shown only when View Message Body = Simple HTML. It looks correct when the message is shown as Original HTML or Plain Text, or when html5.enable=false.
This bug will be fixed by patch proposed to Bug 594646.
See Bug 572886 comment #44, please.
Whiteboard: [View/Message Body As/Simple HTML case] → [View/Message Body As/Simple HTML case] [will_be_fixed_by_Bug 594646]
Hi all, 

Is this bug is fixed? 

I didn't seen it in last years.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: