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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
|
<option type="enum" id="opt/144">
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<arg_longname>
<en>Media 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>150</arg_order>
<arg_spot>A</arg_spot>
<arg_substitution />
<arg_proto> -sMediaType=%s</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>md5k</driver>
<arg_defval>ev/869</arg_defval>
</constraint>
<constraint sense="true">
<driver>md2k</driver>
<arg_defval>ev/869</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/873">
<ev_longname>
<en>Post Card</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>PostCard</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>PostCard</ev_driverval>
</enum_val>
<enum_val id="ev/874">
<ev_longname>
<en>Fine Paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>FinePaper</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>FinePaper</ev_driverval>
</enum_val>
<enum_val id="ev/875">
<ev_longname>
<en>Coated Film</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CoatedFilm</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>CoatedFilm</ev_driverval>
</enum_val>
<enum_val id="ev/876">
<ev_longname>
<en>Glossy Paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>GlossyPaper</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>GlossyPaper</ev_driverval>
</enum_val>
<enum_val id="ev/877">
<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>TransparencyFilm</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>TransparencyFilm</ev_driverval>
</enum_val>
<enum_val id="ev/878">
<ev_longname>
<en>OHP</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>OHP</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>OHP</ev_driverval>
</enum_val>
<enum_val id="ev/879">
<ev_longname>
<en>OHP (MD 2000)</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>OHP_MD2000</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>OHP_MD2000</ev_driverval>
</enum_val>
<enum_val id="ev/869">
<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>PlainPaper</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>PlainPaper</ev_driverval>
</enum_val>
<enum_val id="ev/870">
<ev_longname>
<en>Iron Seal</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>IronSeal</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>IronSeal</ev_driverval>
</enum_val>
<enum_val id="ev/871">
<ev_longname>
<en>Rebeca Free</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>RebecaFree</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>RebecaFree</ev_driverval>
</enum_val>
<enum_val id="ev/872">
<ev_longname>
<en>Cardboard</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CardBoard</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>CardBoard</ev_driverval>
</enum_val>
</enum_vals>
</option>
|
