Certain GIF is printed in white on black bottom with PCL 5

RESOLVED FIXED

Status

()

Core
Printing: Output
RESOLVED FIXED
15 years ago
15 years ago

People

(Reporter: Lee Tartak, Assigned: mkaply)

Tracking

({fixed1.4})

Trunk
x86
OS/2
fixed1.4
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments, 1 obsolete attachment)

(Reporter)

Description

15 years ago
This is a continuation of bug 158472. The fix for that bug took care of all
situations except for Laserjet in non PCL6 mode. If the Laserjet driver is set
to PCL6 or printer specific in any case the image prints correctly.  This is an
OS2 bug only.  Will attach image below.
(Reporter)

Comment 1

15 years ago
Created attachment 114049 [details]
A gif that shows the problem
(Reporter)

Comment 2

15 years ago
Created attachment 114115 [details] [diff] [review]
Patch to fix problem

As part of  processing the image the code creates a temp bitmap in a memory DC.
 The bitmap was created with a color depth of 8 BPP.  In this color depth the
GPI erase filled the background with BLACK for laserjet non PCL6 modes For all
other devices and printer compatible PSs WHITE	is used.  However when the temp
bitmap color depth is set to 24 BPP when creating the background is WHITE as it
should. Since all the printer DCs can handle 24 BPP is better to work in
thatdepth anyway.
(Reporter)

Comment 3

15 years ago
Created attachment 120109 [details] [diff] [review]
New patch to fix problem

Old patch did not work with optimized code.
Attachment #114115 - Attachment is obsolete: true
(Assignee)

Comment 4

15 years ago
taking
Assignee: rods → mkaply
(Assignee)

Comment 5

15 years ago
Comment on attachment 120109 [details] [diff] [review]
New patch to fix problem

r=mkaply, sr=blizzard, a=mkaply
Attachment #120109 - Flags: superreview+
Attachment #120109 - Flags: review+
Attachment #120109 - Flags: approval1.4+
(Assignee)

Comment 6

15 years ago
Fixed on trunk and 1.4
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Keywords: fixed1.4
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.