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
109
110
111
112
113
114
|
<option type="enum" id="opt/68">
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<arg_longname>
<en>Paper type</en>
</arg_longname>
<arg_shortname>
<en>MediaType</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_substitution />
<arg_proto> -dPapertype=%s</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>chp2200</driver>
<arg_defval>ev/613</arg_defval>
</constraint>
<constraint sense="true">
<driver>cdj970</driver>
<arg_defval>ev/613</arg_defval>
</constraint>
<constraint sense="true">
<driver>cdj890</driver>
<arg_defval>ev/613</arg_defval>
</constraint>
<constraint sense="true">
<driver>cdj880</driver>
<arg_defval>ev/613</arg_defval>
</constraint>
<constraint sense="true">
<driver>cdj850</driver>
<arg_defval>ev/613</arg_defval>
</constraint>
<constraint sense="true">
<driver>cdj670</driver>
<arg_defval>ev/613</arg_defval>
</constraint>
<constraint sense="true">
<driver>cdj1600</driver>
<arg_defval>ev/613</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/613">
<ev_longname>
<en>Plain paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>plain</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>0</ev_driverval>
</enum_val>
<enum_val id="ev/614">
<ev_longname>
<en>Bond paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>bond</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/615">
<ev_longname>
<en>Special paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>special</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/616">
<ev_longname>
<en>Glossy film</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>glossy</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/617">
<ev_longname>
<en>Transparency film</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>transparency</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>
</enum_val>
</enum_vals>
</option>
|
