289457 - View->Message Body->As Plain Text does not use my font selections

Status: RESOLVED INVALID

(Thunderbird :: Mail Window Front End, defect)

Description

[Doug Hockin]

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

View->Message Body->As Plain Text does not use my font selections

Thunderbird 1.0.2 on Windows XP

When HTML is sanitized to plain text, my font selections (those I've
set for the display of plain text messages) are not respected.  It
uses the default settings, rather than mine.



Reproducible: Always

Steps to Reproduce:
1. In Tools->Options->Fonts make some non-default settings for display.
2. In View->Message Body, select "As Plain Text".
3. Have somebody (or yourself) send you an HTML mail message.

Actual Results:  
HTML message displays with default fonts/sizes/styles.

Expected Results:  
Used my choosen font settings.

Comment 1

[Mike Cowperthwaite]

Note that font selections need to be made for each individual language group 
(the dropdown at the top of the Fonts options page).  If someone sends you an 
email that specifies a charset of, say, windows-1251, even if it contains 
vanilla ASCII, the fonts will be selected from the settings for the Cyrillic 
language group.

Comment 2

[Doug Hockin]

Attachment: Example of email to which problem happens.

I don't think the suggestion that the problem might be emails in a different
language applies, but I could be wrong as I'm not very experienced at reading
the meaning of the email headers.  Here's an example that has the problem.
I can provide others if needed.  I have a couple of email lists I'm
on where the problem happens to all their emails.

Comment 3

[Doug Hockin]

I figured out how to read the message header and saw that these messages
are Unicode (UTF-8).  I changed the font display settings for Unicode and the
problem is fixed -- well mostly.  Turns out there appear to be errors
in the conversion of this mime encoded HTML to plain text, I think
related to tags that bridge end of lines, where MIME sticks '='.  Will submit as
a separate problem if it's not reported already.