[cups.bugs] [HIGH] STR #4246: UserCode incorrectly handled for Ricoh printers
Jevon Longdell
jevon.longdell at gmail.com
Fri Dec 7 07:23:57 PST 2012
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New]
We have Ricoh printers and have to provide user code with print jobs for
accounting reasons, and this doesn't work.
According to this page http://moore.cx/experiences/ricoh_user_code.html it
looks like you insert some code in to the "%%BeginProlog" section of the
postscript file. When I do this edit by hand everything works well and
print the result everything works fine. When I get cups to do it for me it
stuffs it up.
The desired lines in the postscript look like
....
%%BeginProlog
mark
() (112233) (200502071842) {setuserinfo} stopped
cleartomark
....
%%EndProlog
Where 112233 is the usercode and 2005... is a datestamp.
The ppd I'm using is the standard ricoh one
(https://www.dropbox.com/s/2o75ur3z74n732s/ricoh3colour.ppd), that was
edited as per the instructions on the openprinting website (see
http://tiny.cc/hq8wow) to put in my usercode.
It has lines in it that are:
*DefaultUserCode: 112233
*UserCode None/None: ""
*UserCode 112233/112233: "%% FoomaticRIPOptionSetting: UserCode=112233"
*FoomaticRIPOptionSetting UserCode=112233: "mark\n&&
() (112233) (20`date +%y%m%d%R | sed 's/://'`) {setuserinfo} stopped\n&&
cleartomark\n"
*End
And to my untrained eye look like they are asking foomatic-rip to make the
appropriate change to the postscript file.
However the relevant section of the postscript generated by foomatic-rip
doesn't look right (and doesnt work) it looks like:
[{
%%BeginFeature: *CustomLockedPrintPassword True
()
%%EndFeature
} stopped cleartomark
[{
%%BeginFeature: *UserCode 112203
%% FoomaticRIPOptionSetting: UserCode=112203
%%EndFeature
} stopped cleartomark
[{
%%BeginFeature: *RIWatermark Off
%%EndFeature
and my job gets rejected.
Link: https://www.cups.org/str.php?L4246
Version: 1.6.1
More information about the cups-devel
mailing list