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
|
<option type="enum" id="opt/190">
<!-- 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>100</arg_order>
<arg_spot>A</arg_spot>
<arg_pjl />
<arg_proto>SET MEDIASOURCE=%s</arg_proto>
</arg_execution>
<constraints>
<constraint sense="false">
<make>HP</make>
<model>LaserJet 4050</model>
<arg_defval>ev/964</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/963">
<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>TRAY3</ev_driverval>
</enum_val>
<enum_val id="ev/964">
<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>TRAY0</ev_driverval>
</enum_val>
<enum_val id="ev/965">
<ev_longname>
<en>Tray 3</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Tray3</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>TRAY1</ev_driverval>
</enum_val>
<enum_val id="ev/966">
<ev_longname>
<en>Tray 4</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Tray4</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>TRAY2</ev_driverval>
</enum_val>
</enum_vals>
</option>
|
