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
|
<option type="enum" id="opt/hl7x0-InputSlot">
<!-- 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>120</arg_order>
<arg_spot>J</arg_spot>
<arg_required />
<arg_substitution />
<arg_proto>%s</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>hl7x0</driver>
<arg_defval>ev/hl7x0-InputSlot-Default</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/hl7x0-InputSlot-Default">
<ev_longname>
<en>Printer Default</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Default</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval></ev_driverval>
</enum_val>
<enum_val id="ev/hl7x0-InputSlot-Auto">
<ev_longname>
<en>Automatic Selection</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Auto</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>o</ev_driverval>
</enum_val>
<enum_val id="ev/hl7x0-InputSlot-Tray1">
<ev_longname>
<en>Tray 1</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Tray1</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/hl7x0-InputSlot-Tray2">
<ev_longname>
<en>Tray 2</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Tray2</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/hl7x0-InputSlot-MultiPurpose">
<ev_longname>
<en>Multi Purpose Tray</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>MultiPurpose</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>O</ev_driverval>
</enum_val>
<enum_val id="ev/hl7x0-InputSlot-Manual">
<ev_longname>
<en>Manual Feed</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>M</ev_driverval>
</enum_val>
</enum_vals>
</option>
|
