blob: 33fa1a61268ca4def8c94b6da708b817185c1369 (
plain)
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
|
<option type="enum" id="opt/1">
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<arg_longname>
<en>Ink Type</en>
</arg_longname>
<arg_shortname>
<en>InkType</en><!-- backends only know <en> shortnames! -->
</arg_shortname>
<arg_execution>
<arg_group>General</arg_group>
<arg_order>100</arg_order>
<arg_spot>B</arg_spot>
<arg_substitution />
<arg_proto>%s</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>lm1100</driver>
<arg_defval>ev/lm1100-Color</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/lm1100-Color">
<ev_longname>
<en>Color cartridge</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Color</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/lm1100-Black">
<ev_longname>
<en>Black cartridge</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Black</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval> -bw</ev_driverval>
</enum_val>
</enum_vals>
</option>
|
