Bug 692545 - Page 2 rendered badly
Summary: Page 2 rendered badly
Status: NOTIFIED INVALID
Alias: None
Product: GhostPCL
Classification: Unclassified
Component: PCL interpreter (show other bugs)
Version: master
Hardware: PC All
: P2 normal
Assignee: Marcos H. Woehrmann
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-27 01:54 UTC by Marcos H. Woehrmann
Modified: 2011-11-09 18:26 UTC (History)
0 users

See Also:
Customer: 210
Word Size: ---


Attachments
course description 2 pages (2.11 MB, application/pdf)
2011-09-27 16:33 UTC, Henry Stiles
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos H. Woehrmann 2011-09-27 01:54:35 UTC
The customer reports and I've verified that GhostPCL renders page 2 of the attached PCL file very badly.  Much of the content is missing and the rest is shifted to the left.  I've printed the file to my HP P3005 and HP 4500 and both print the page reasonably.

The command line I'm using for testing:

  ./main/obj/pcl6 -sDEVICE=ppmraw -o test.ppm ./2p.pcl
Comment 1 Henry Stiles 2011-09-27 14:26:09 UTC
The result matches my HP printer.  Can you check yours?
Comment 2 Marcos H. Woehrmann 2011-09-27 14:58:45 UTC
Created attachment 7935 [details]
ghostscript.pdf
Comment 4 Marcos H. Woehrmann 2011-09-27 15:00:50 UTC
(In reply to comment #1)
> The result matches my HP printer.  Can you check yours?

I've attached output from Ghostscript and an HP printer (this was supplied by the customer but my results are the same).  Could you please attach output from your HP printer and supply the model number?
Comment 5 Henry Stiles 2011-09-27 16:33:17 UTC
Created attachment 7939 [details]
course description 2 pages

Very odd here are both pages printed on an HP Color Laserjet 4600.
Comment 6 Henry Stiles 2011-09-28 21:04:01 UTC
Wasn't sure if I was supposed to pass the ball back or not - if in doubt I pass it.
Comment 7 Marcos H. Woehrmann 2011-10-05 19:57:28 UTC
I've notified the customer that the HP color laserjet 4600 prints the same file the same way we process it and therefore we don't consider this a bug.