91506 - Editing forwarded non-ascii mail as new is quoting garbage

Status: VERIFIED WORKSFORME

(MailNews Core :: Internationalization, defect, P2)

Description

[marina]

This bug is different from 41009 that deals with NoMime or wronly labeled
messages. This bug is about forwarding a non-ascii message that has a correct
Mime info in the header and body but still is quoted as garbage when Edited as new.
Steps to reproduce:
- go to the newsgroup ( i'll attach the message later);
- select a Mime-encoded message;
- forward message ( my settings are as attachment);
- get the message, select it( note: the display is correct at this time);
- click Message|Edit as new;
//note: the message display is incorrect ( not only it looks like one paragrapgh
, this problem was already reported) but the message body is quoted as garbage
and there is no workaround to correct the display

Comment 1

[marina]

Attachment: here is a forwarded message from relcom.cinema that has mime info in it

Comment 2

[marina]

yes, and i forgot to mention that if i don't forward this type of message but
just select it before forwarding and click Edit as new the display would be
correct , as oppose to 41009.

Comment 3

[nhottanscp]

If I try this with ASCII message, the body is not quoted because it was
forwarded as an attachment. That should also be the behavior for non ASCII messages.
Reassign to ducarroz, please take a look at this, I don't know where Edit New is
implemented.

Comment 4

[Jean-Francois Ducarroz]

Editing as new is equal to opening a draft.

Comment 5

[scottputterman]

moving to 0.9.7

Comment 6

[marina]

changing qa contact

Comment 7

[marina]

well editing Draft for Nomime messages is still quoting it as garbaled but i
don't see this problem with Editing as new a forward non-ascii nomime message>
Did we already implememnted the behavior for editing frw ascii messages ( no
body is quoted)??? 

Comment 8

[nhottanscp]

Does this still happen?

Comment 9

[Barry Marshall (at work)]

Is this the same problem?  If so, I just got burned by this just this morning.   

With 2002041103 in US localization, I can't forward a note from someone with the
header below in France.  The only way I can get the info is by cutting and
pasting the text from the Preview panel.  Names changed to blah to protect the
guilty  :-)  :

Subject: Blah
From: <blah>
Date: Fri, 12 Apr 2002 10:46:51 +0200 (CEST)
To: blah
X-UIDL: <[e-mail]>
X-Mozilla-Status: 0003
X-Mozilla-Status2: 00000000
Return-Path: <blah>
Received: from blah ([blah]) by fep02-mail.bloor.is.net.cable.rogers.com
(InterMail vM.5.01.04.13 201-253-122-122-113-20020313) with ESMTP id
<2[e-mail]>
for <blah>; Fri, 12 Apr 2002 04:51:05 -0400
Received: from localhost (blah) by cdfpc48.in2p3.fr (8.11.2/8.11.2) with ESMTP
id g3C8kpZ15431 for <blah>; Fri, 12 Apr 2002 10:46:51 +0200
X-Authentication-Warning: cdfpc48.in2p3.fr: blah owned process doing -bs
X-X-Sender: <blah>
Message-ID: <[e-mail]>
MIME-Version: 1.0 
Content-Type: TEXT/PLAIN; charset=X-iso88591
Content-Transfer-Encoding: 8BIT

Comment 10

[nhottanscp]

>Content-Type: TEXT/PLAIN; charset=X-iso88591
The charset above is invalid. This bug is about either no charset specified or
wrong charset is specified (i.e. label charset and content's charset does not
match).

Comment 11

[nhottanscp]

Quoting from the original report.
>This bug is about forwarding a non-ascii message that has a correct
>Mime info in the header and body but still is quoted as garbage when 
>Edited as new.

Marina, does this still happen?

Comment 12

[marina]

I don't see it happening any longer: the body in case of forwarding as
attachment is not quoted (same as ascii implementation). Thanks! Soling as WFM

Comment 13

[marina]

verifying as WFM