Hello,
I really liked PDQ, the way it spools my jobs etc. but
there is a serious bug in version 2.2.1,
that is: Trying to print a file from STDIN (in this
case Mozilla Firefox 0.9.1) results in an incorrect
PostScript code being stored in JOBID.raw file, thus,
causing Ghostscript to report error:
Error: /undefined in ddef
Operand stack:
--nostringval-- UniDict --dict:18/1051(L)-- 50 two
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-
lse 1 %stopped_push 2 3 %oparray_pop 2 3 %oparray_pop 2 3
%oparray_pop 2 3 %oparray_pop .runexec2 --nostringval--
--nostringva
l-- --nostringval-- 2 %stopped_push --nostringval--
Dictionary stack:
--dict:1165/1686(ro)(G)-- --dict:0/20(G)--
--dict:89/200(L)-- --dict:18
/1051(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 4100
I've been looking at this file and found out something odd:
A line which should look like:
16#0032 /two def
Is looking like:
16#0032 /two ddef
(have you noticed the additional "d" letter? this is
the cause of problem I think)
I've included sample ps file so that you can see what I
mean.Printing the same file through foomatic-rip
doesn't show any errors.No errors are also shown when
printing the same file as follows:
1.In Mozilla Firefox set it to print to printer and
then setup printing command as:
cat - > /your_path/file_name.ps
2.run pdq /your_path/file_name.ps
No problems with that...
And one more thing to note is that XPDQ doesn't have
this problem, prints both from STDIN and File
flawlessly.There must be something in PDQ code that
intercepts data from STDIN.Please, take a look at
that.Please, Let me know when you find something or
even release a patch.
Cheers.
Sample html and ps that show errors.