Bad print output from ajax client

[gnyce]

Has anyone seen this before? Have searched, no joy so far... using FF3 to Zimbra using advanced/ajax client, printing some emails, the output is gibberish. See attached for example. I've tried two different printers, even printing using PDFCreator (which gives different results, but still not correct). Yet, if I switch to the Standard/html client, it will print just fine, no problem at all.

Seems odd, and I can seem to reproduce... for example, perhaps it is how the ajax client deals with slightly malformed html from old Groupwise or Notes mail clients? I do have the Pref/Mail/Display Mail as Text set...

thanks,
Greg

[Dirk]

I have exactly the same problem, you are not alone.

I'm pretty sure I know what is causing it, and I have an open support case for it at the moment, expect a fix/patch soon.

[mmorse]

Besides the span style=font-family:courier vs family:monospace discovery, Bug 29379 - printing from firefox 3 ( ff3 ) issues has been filed.

[hurstel]

I had the same issue this morning. I was able to resolve it by running firefox -P at the start prompt on my XP machine and creating a new profile. Seems like more a Firefox issue than Zimbra.

[swu]

I have the same issues and I read through the referenced bugzilla but I am unclear as to which version it has been fixed in. It's probably in the bug report, but I don't see it.

<< this bug is fixed. Now the css uses monospace instead of courier. >>

Thx - Steve

[phoenix]

Originally Posted by swu

I have the same issues and I read through the referenced bugzilla but I am unclear as to which version it has been fixed in. It's probably in the bug report, but I don't see it.

It was in the comment you've quoted from:

this bug is fixed. Now the css uses monospace instead of courier.

build: Release 5.0.9_GA_2525.RHEL4_20080811184555 RHEL4 NETWORK edition

i.e. 5.0.9

[sdrury]

Is this still an issue with people? We are having this problem with 'some' users and can fix 'some' by updating printer drivers...some it seems we are unable to fix.
Regards,
Sean.

[Cryophallion]

While this appeared to be fixed previously, it seems there is a regression in FF 3.6.2 that brings this back. I used zimbra desktop for a while to get around it, now I am going to try chrome, although I know I will seriously miss the awesome bar...