blob: 95debb178e2938c7d30752e4d3bd764e8f69bc4b (
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
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
|
<option type="enum" id="opt/13">
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<arg_longname>
<en>Ghostscript Bits Per Pixel</en>
</arg_longname>
<arg_shortname>
<en>BitsPerPixel</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> -dBitsPerPixel=%s</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>bjc800</driver>
<arg_defval>ev/155</arg_defval>
</constraint>
<constraint sense="true">
<driver>bjc600</driver>
<arg_defval>ev/155</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/155">
<ev_longname>
<en>CMYK with FS dithering (24 bpp)</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>24</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>24</ev_driverval>
</enum_val>
<enum_val id="ev/154">
<ev_longname>
<en>CMYK with FS dithering (32 bpp)</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>32</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>32</ev_driverval>
</enum_val>
<enum_val id="ev/156">
<ev_longname>
<en>CMYK with Ghostscript FS dithering (16bpp)</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>16</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>16</ev_driverval>
</enum_val>
<enum_val id="ev/822">
<ev_longname>
<en>CMYK with Ghostscript dithering (8bpp)</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>8</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>8</ev_driverval>
</enum_val>
<enum_val id="ev/157">
<ev_longname>
<en>Monochrome (1bpp)</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>1</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_vals>
</option>
|
