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
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
<option type="enum" id="opt/213">
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<arg_longname>
<en>Media Source</en>
</arg_longname>
<arg_shortname>
<en>InputSlot</en><!-- backends only know <en> shortnames! -->
</arg_shortname>
<arg_execution>
<arg_group>General</arg_group>
<arg_order>150</arg_order>
<arg_spot>Z</arg_spot>
<arg_postscript />
<arg_proto><</InputAttributes <<0 null %s <</PageSize [6 6 524287 524287] >> >> >> setpagedevice</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>pcl3</driver>
<arg_defval>ev/1040</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/1040">
<ev_longname>
<en>Standard Tray</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Tray</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>1</ev_driverval>
</enum_val>
<enum_val id="ev/1041">
<ev_longname>
<en>Manual Feeder</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Manual</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>2</ev_driverval>
</enum_val>
<enum_val id="ev/1042">
<ev_longname>
<en>Envelope Feeder</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Envelope</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>3</ev_driverval>
</enum_val>
<enum_val id="ev/1043">
<ev_longname>
<en>Desktop CSF</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>DesktopCSF</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>4</ev_driverval>
<constraints>
<constraint sense="true">
<make>Generic</make>
<model>PCL 3 Printer</model>
<driver>pcl3</driver>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="true">
<make>HP</make>
<model>DeskJet 340C</model>
<driver>pcl3</driver>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<driver>pcl3</driver>
<arg_defval>na</arg_defval>
</constraint>
</constraints>
</enum_val>
<enum_val id="ev/1044">
<ev_longname>
<en>Banner Printing</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Banner</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>-1</ev_driverval>
</enum_val>
</enum_vals>
</option>
|
