Closed Bug 289611 Opened 20 years ago Closed 16 years ago

Errors when converting HTML to plain text (View->Message Body->As Plain Text)

Categories

(MailNews Core :: MIME, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 122876

People

(Reporter: douger34, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: testcase)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 When converting HTML to plain text (View->Message Body->As Plain Text), tags broken across end of lines by the MIME formatting are (sometimes?) misinterpreted or missed. In the attachment, a closing </i> tag is split across the MIME end of line (I don't know much about MIME) resulting in much of the message being displayed as italic. There are also extraneous '/' slashes that appear in the Plain Text that may also be conversion errors. Personally, I think the italic tags should have been disregarded completely in the conversion, so there is no style in the plain text, but if it's going to keep the italic, it needs to do it right. Reproducible: Always Steps to Reproduce: 1. Set View->Message Body->As Plain Text 2. Send the attached email to yourself (?) 3. View the email Actual Results: The closing tag of a <i></i> pair appears to have been missed and a large part of the email ended up in italic. Expected Results: Only the part between the <i></i> tags should have ended up in italic. Or my person preference is for all style tags to be disregarded and the result should be unstyled plain text.
This email when viewed in Thunderbird set to show HTML emails as plain text, display an error (errors?) in convertion. A closing </i> tag is apparently missed because it ended up broken across the MIME end of line. Also there are extraneous '/' slashes displayed at various places.
The xref'd bug 230423, is indeed very similar. The only difference I can see is that some of the follow on explanation in the middle of that bug attributes it to tags inside of HTML tables. The email I included with this bug has no tables in it at all and I'm inclined to think this bugreport has something to do with my suggestion of tags being broken over the MIME end of line boundaries. bug 230423 also confirms that the conversion to plain text, as currently implemented, is attempting to keep some styles like italic and bold, with I disagree with. In my opinion, that's not plain text, that's "Very Simple HTML", but maybe there's something I'm missing as to the reasoning for doing it that way.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
I still get the same error when opening the attachement.
QA Contact: front-end
Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is 2.0.0.16)
Whiteboard: closeme 2008-08-28
I just opened the included .eml file with TB 2.0.0.16 and it still happens. The site that email came from has gone out of existence and I haven't gotten an email that displayed that problem from anywhere else for some time. It would be nice if the problem was fixed, but perhaps it's so obscure that the priority should be low.
Version: unspecified → 2.0
Assignee: mscott → nobody
Severity: normal → minor
Whiteboard: closeme 2008-08-28
Keywords: testcase
Confirming this behavior in both TB Shredder and SM 2.0pre-whatever. Moving to Core; setting dependency.
Status: UNCONFIRMED → NEW
Component: Mail Window Front End → Backend
Depends on: 230423
Ever confirmed: true
Product: Thunderbird → MailNews Core
QA Contact: front-end → backend
Version: 2.0 → Trunk
Component: Backend → MIME
QA Contact: backend → mime
I just recently received an airline flight Trip Summary and Receipt email from NWA and it happen twice in one email. TB 2.0.0.23.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: