Closed Bug 310315 Opened 19 years ago Closed 17 years ago

Displaying of mails that contain text/plain and text/html (redundant)

Categories

(Thunderbird :: Mail Window Front End, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 130119

People

(Reporter: Andreas_Kleinert, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 This is more a feature request than a bug - but then again also a bug, possibly. I keep getting eMails from someone using "Lotus Notes Release 6.0.2CF1". Every eMail he sends does contain two versions of the text body. One is text/plain and the other one is text/html. The content is identical, but the formatting is not. Since I did not (want to) disable HTML display completely in Thunderbird, it keeps displaying the HTML version - which seems to be the default. What I am missing, is an option to override that default behaviour, i.e. if an eMail contains "alternative" parts, it should be possible to define which alternative should be used in such a case. Here are the relevant MIME headers: --=_alternative 004F7ADF8625708A_= Content-Type: text/plain; charset="US-ASCII" ... --=_alternative 004F7ADF8625708A_= Content-Type: text/html; charset="US-ASCII" ... The annyoing factor here is, that the HTML version uses <font size=2> everywhere, which renders to very small sized Courier (less than 8pt I would say) which is also an annoying default. Reproducible: Always Steps to Reproduce:
(In reply to comment #0) > Since I did not (want to) disable HTML display completely in Thunderbird, it > keeps displaying the HTML version - which seems to be the default. > > What I am missing, is an option to override that default behaviour, i.e. if an > eMail contains "alternative" parts, it should be possible to define which > alternative should be used in such a case. This doesn't make sense. In the first paragraph, you imply that you know how to "disable HTML display" and in the next paragraph, you imply that you don't. > The annyoing factor here is, that the HTML version uses <font size=2> > everywhere, which renders to very small sized Courier (less than 8pt I would > say) which is also an annoying default. You can set a minimum font size for display, in the Options | Display | Fonts dialog (whoops! you're using 1.0.x, you'll have to find the equivalent in the old style options dialog). Note that this setting is actually stored on a per- language-group basis -- the language group is specified at the top of the page, so you may need to select several different ones and set the min.font size accordingly, depending on what kinds of mail you get.
QA Contact: front-end
(In reply to comment #1) > (In reply to comment #0) > > Since I did not (want to) disable HTML display completely in Thunderbird, it > > keeps displaying the HTML version - which seems to be the default. > > > > What I am missing, is an option to override that default behaviour, i.e. if an > > eMail contains "alternative" parts, it should be possible to define which > > alternative should be used in such a case. > > This doesn't make sense. In the first paragraph, you imply that you know how to > "disable HTML display" and in the next paragraph, you imply that you don't. What the OP means is that when viewing a multipart/alternative message with text and HTML versions there is no way to see the text version. No amount of frigging with the "View -> Message Body as" menu lets you see the text/plain part of the message. I ran into this composing an invite for a party, where the text part of the message had a text version of the invite and the HTML part had just an inline image version with nice layout and pictures... but no text. So Thunderbird shows a blank message if you set View->Message Body As->Plain Text. And I think that is the bug in a nutshell.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.