Summary: | pxlcolor device output not correct | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | George Liu <george.liu> |
Component: | Printer Driver | Assignee: | Marcos H. Woehrmann <marcos.woehrmann> |
Status: | NOTIFIED FIXED | ||
Severity: | normal | CC: | htl10 |
Priority: | P4 | ||
Version: | 8.15 | ||
Hardware: | Macintosh | ||
OS: | MacOS X | ||
Customer: | Word Size: | --- | |
Attachments: |
this file will generate invalid pxl file.
The pcl-xl file generated by the attached postscript file patch |
Description
George Liu
2007-09-27 15:57:01 UTC
Created attachment 3418 [details]
this file will generate invalid pxl file.
Hmm, sometime ago, pxlmono/pxlcolor used to differ only by a PJL wrapper switching the color mode at the PJL level. Bug #688320 demonstrates the same problem. Maybe these two bugs has the same root cause. -------------------------------------------------------- The pxlcolor driver sometimes outputs unusable output of images. The output is "ExtraData" by HP printer and also by GhostPCL. A look into the PCL6 stream finds that the ReadImage operator is fed with extra data, e.g., the page colorspace is eGray, the image is e8Bit and 8x1 pixels large, but the ReadImage is fed with 24 bytes instead of 8 bytes. -------------------------------------------------------- I modified the generated PCL-XL data, replaced c0 01 f8 03 6a (set colorspace=eGray) with c0 02 f8 03 6a (set colorspace=eRGB). It still cannot print. I'm having trouble duplicating this bug. Ghostscript 8.15 generates an error when converting the attached: /invalidfont in --xshow-- More recent versions of Ghostscript read the input file but generate PCL-XL output which prints fine on both my HP LaserJet 6MP and my LaserJet 4500. Created attachment 3466 [details]
The pcl-xl file generated by the attached postscript file
The pcl-xl file generated by the attached postscript file using command line
cat ~/Download/attachment.cgi | gs -q -dBATCH -dPARANOIDSAFER -dNOPAUSE
-sDEVICE=pxlcolor -r600x300 -sPAPERSIZE=letter -sOutputFile=- - > junk.pxl
I installed GS 8.60 and did the same test (submit the attached Postscript).
Printer will not print. still see colorspace set to eGrey.
> More recent versions of Ghostscript read the input file but generate PCL-XL
output which prints fine on both my HP LaserJet 6MP and my LaserJet 4500.
What version of Ghostscript is it?
Sorry, but I'm confused. The title of the bug and your original comment refers to pxlmono, but you've attached a PCL-XL file written using pxlcolor. Which device are you having trouble with? Sorry, I have trouble with pxlcolor. pxlmono works fine. (I thought pxlmono == pxlcolor) okay, now I can reproduce the problem. With pxlcolor and gs860 my HP 6MP prints InternalError 0x26 and the HP 4500 prints ExtraData. I'll investigate further. This problem is caused by the pxl output stream being in the wrong colorspace when the image data appears. Inserting an ubyte eRGB ColorSpace SetColorSpace before the BeginImage operator at position 3501 allows this file to be printed on my HP 4500 and HP 6MP and also allows GhostPCL 1.50 to read the file. I'm in the process of fixing gdevpx.c and expect to have a patch soon. Created attachment 3471 [details]
patch
Fixed in r8290 (see attached patch). I downloaded the latest Ghostscript svn. build 8291. (The change in patch appeared in source code) I compiled gs from source and gs -h showed pre-8.61 release.(Aug-02) Print to HP 5500 and got the following error: PCL XL error Subsystem: IMAGE Error: ExtraData Operator: ReadImage Position: 3506 I've tested the output on an HP 4100, 4500, and 6MP and using GhostPCL, all work with the latest pxlcolor device. Can you attach the pxl file? A minor correction: pxlcolor output does not print on my HP LaserJet 6MP, generating an InternalError 0x26 at position 417. I believe this is because the 6MP is a monochrome device and can't handle color PCL-XL images. I think my problem (HP5500 won't print) might be a driver rather than Ghostscript problem. I can use ghostscript command line and generate a valid PCL-XL data that can print on HP5050N. This issue can now be closed as fixed. Thank you. |