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
|
<option type="enum" id="opt/lz11-V2-PageSize">
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<arg_longname>
<en>Page Size</en>
</arg_longname>
<arg_shortname>
<en>PageSize</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> --papersize=%s</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>lz11-V2</driver>
<arg_defval>ev/lz11-V2-PageSize-A4</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/lz11-V2-PageSize-A6">
<ev_longname>
<en>A6</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>A6</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a6</ev_driverval>
</enum_val>
<enum_val id="ev/lz11-V2-PageSize-A5">
<ev_longname>
<en>A5</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>A5</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a5</ev_driverval>
</enum_val>
<enum_val id="ev/lz11-V2-PageSize-A4">
<ev_longname>
<en>A4</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>A4</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a4</ev_driverval>
</enum_val>
<enum_val id="ev/lz11-V2-PageSize-Letter">
<ev_longname>
<en>US Letter</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Letter</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>letter</ev_driverval>
</enum_val>
<enum_val id="ev/lz11-V2-PageSize-Legal">
<ev_longname>
<en>US Legal</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Legal</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>legal</ev_driverval>
</enum_val>
<enum_val id="ev/lz11-V2-PageSize-HalfLetter">
<ev_longname>
<en>Half Letter</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>HalfLetter</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>halfletter</ev_driverval>
</enum_val>
</enum_vals>
</option>
|
