-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathPPD-README
69 lines (53 loc) · 3.24 KB
/
PPD-README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
Creating PPDs for printers
==========================
Adding support to exiting PPDs for other sharp printers should be pretty
straight forward though. Please be aware, that this guide was created by
someone with little knowledge about PPDs. There may be quirks, unneccary
steps, things that are plainly wrong or the guide is missing things ...
First of all set some cups specific options. These should be put in the
header section:
*cupsVersion: 1.0
*cupsManualCopies: False
*cupsModelNumber: 1
*cupsFilter: "application/vnd.cups-postscript 100 sharp-postprocess"
Note: Only set ManualCopies to False, if you add the QTY dummy later on, and
your printer supports this @PJL QTY option.
Next we need to setup the PJL correctly. You will likely have these options
already set in the PPD file somewhere, if that is the case modify them.
What we do here, is to add placeholders into the PJL header, that are later
on replaced by the postprocess script.
*Protocols: PJL
*JCLBegin: "<1B>%-12345X@PJL JOB<0A>"
*JCLToPSInterpreter: "@PJL COMMENT XSHARP_USERNAME=<22>XSHARP_USERNAME<22><0A>@PJL COMMENT XSHARP_SPOOLTIME=<22>XSHARP_SPOOLTIME<22><0A>@PJL ENTER LANGUAGE = POSTSCRIPT <0A>"
*JCLEnd: "<1B>%-12345X@PJL EOJ<0A><1B>%-12345X"
The postprocessor will replace these comments with the real commands
(ie. @PJL COMMENT XSHARP_USERNAME="XSHARP_USERNAME" is replaced with
@PJL USERNAME="unixuser")
The next thing we need to do is to add the ability to specify the username
and password. For this, add the following to the PPD:
*OpenGroup: Authentication/User Authentication
*% **** AccountLogin ***********************************************************
*OpenUI *AccountLogin/Username: PickOne
*OrderDependency: 23 JCLSetup *AccountLogin
*DefaultAccountLogin: ALDBusAsk
*AccountLogin ALKeyNone/No Username: ""
*AccountLogin ALDBusAsk/Ask Later: "@PJL COMMENT XSHARP_ACCOUNTLOGIN=<22>XSHARP_AES_ENCRYPT:XSHARP_ASK_STRING:Username:XSHARP_ASK_STRING:XSHARP_AES_ENCRYPT<22><0A>"
*CloseUI: *AccountLogin
*CustomAccountLogin True: "@PJL COMMENT XSHARP_ACCOUNTLOGIN=<22>XSHARP_AES_ENCRYPT:\1:XSHARP_AES_ENCRYPT<22><0A>"
*ParamCustomAccountLogin Login/Username: 1 string 0 255
*% *****************************************************************************
*% **** AccountPassword ********************************************************
*OpenUI *AccountPassword/Password: PickOne
*OrderDependency: 24 JCLSetup *AccountPassword
*DefaultAccountPassword: APDBusAsk
*AccountPassword APKeyNone/No Password: ""
*AccountPassword APDBusAsk/Ask Later: "@PJL COMMENT XSHARP_ACCOUNTPASSWORD=<22>XSHARP_AES_ENCRYPT:XSHARP_ASK_PASSWORD:Password:XSHARP_ASK_PASSWORD:XSHARP_AES_ENCRYPT<22><0A>"
*CloseUI: *AccountPassword
*CustomAccountPassword True: "@PJL COMMENT XSHARP_ACCOUNTPASSWORD=<22>XSHARP_AES_ENCRYPT:\1:XSHARP_AES_ENCRYPT<22><0A>"
*ParamCustomAccountPassword Password/Passwort: 1 password 0 31
*% *****************************************************************************
*CloseGroup: Authentication
Please note, that it may be a good idea not to include the Custom option (the
last two lines for each option). These never show up in many applications, and
may cause trouble in others. Please refere to the BUGS section in the README.
That should be all that is neccessary.