Thunderbird 2.0.0.6 - Odd printing problems

[NoOp]

On 08/07/2007 02:54 AM, Jonathan Kaye wrote:
> NoOp wrote:
> 
>> I've experienced a very odd printing problem Thunderbird 2.0.0.6  that I
>> can't quite figure out. The symptoms are exactly the same with
>> w/SeaMonkey 1.1.4 (linux). Note: both Thunderbird & SeaMonkey were
>> recently updated by Mozilla due to security issues.
>> 
>> Problem: I cannot print an email message to my default CUPS printer. The
>> CUPS printer monitor will show that the message is printing, I wait, and
>> I wait, and the job never prints. The interesting part is that I *can*
>> print a newsgroup message (such as this one) with no problems at all,
>> and *can* print a web page. It's only email messages that are not
>> printing. It does not matter if I restart CUPS, clear the CUPS cache,
>> nothing works. Additionally, the same symptom occurs when printing from
>> my network connected (via SAMBA) machines. All other applications
>> (OpenOffice, Text, etc., etc.) print fine - ditto for the networked
>> machines.
>> 
>> Anyone else experiencing this problem?
>> 
>> Ubuntu 7.04 2.6.20-16-386
> Hi NoOp,
> I'm using Debian (not Ubuntu) with a 2.6.22 kernel and like you just got an
> auto-update 2.0.0.6 from TB. I just tried printing from TB on my Cups
> printer and it works with no problem. Printing is normal. I did have to
> change the page size on the Print properties of TB. It had reverted back to
> 8.5"x11" and I had to reset it to A4. It did print before I did this but
> maybe your printer is fussier than mine? Do you see your Cups printer in
> the File -> Print... menu? Are the properties as they should be?
> Cheers,
> Jonathan

I've finally narrowed it down to what appears to be a font problem in
Thunderbird/SeaMonkey. I can print anything (even Chinese) from other
applications, and in TB/SM I can print a received ISO-8859-1 msg, but
cannot print a msg that was sent in ISO-8859-1 *and replied to* in
ISO-8859-1. My systems are set up for UTF-8 in locales, and recently I
changed my TB/SM settings to ISO-8859-1 so that my postings would be a
little easier for others to read (my UTF-8 fonts were too small). So I
think that has something to do with it as I've backed down to SM 1.1.2 &
1.1.3 with no change.