File: 131.xml

package info (click to toggle)
foomatic-db 20061031-1
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 113,544 kB
  • ctags: 3
  • sloc: xml: 183,110; sh: 153; makefile: 123
file content (146 lines) | stat: -rw-r--r-- 5,069 bytes parent folder | download | duplicates (3)
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
<option type="enum" id="opt/131">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Resolution</en>
  </arg_longname>
  <arg_shortname>
   <en>Resolution</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> -r%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>lxm3200</driver>
      <arg_defval>ev/844</arg_defval>
     </constraint>
     <constraint sense="true">
      <driver>lxm3200-tweaked</driver>
      <arg_defval>ev/844</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/840">
    <ev_longname>
     <en>300x300 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>300x300dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>300x300</ev_driverval>
   </enum_val>
   <enum_val id="ev/841">
    <ev_longname>
     <en>300x600 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>300x600dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>300x600</ev_driverval>
   </enum_val>
   <enum_val id="ev/842">
    <ev_longname>
     <en>300x1200 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>300x1200dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>300x1200</ev_driverval>
   </enum_val>
   <enum_val id="ev/843">
    <ev_longname>
     <en>600x300 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>600x300dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>600x300</ev_driverval>
   </enum_val>
   <enum_val id="ev/844">
    <ev_longname>
     <en>600x600 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>600x600dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>600x600</ev_driverval>
   </enum_val>
   <enum_val id="ev/845">
    <ev_longname>
     <en>600x1200 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>600x1200dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>600x1200</ev_driverval>
   </enum_val>
   <enum_val id="ev/846">
    <ev_longname>
     <en>1200x300 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>1200x300dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>1200x300</ev_driverval>
   </enum_val>
   <enum_val id="ev/847">
    <ev_longname>
     <en>1200x600 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>1200x600dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>1200x600</ev_driverval>
   </enum_val>
   <enum_val id="ev/848">
    <ev_longname>
     <en>1200x1200 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>1200x1200dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>1200x1200</ev_driverval>
   </enum_val>
  </enum_vals>
</option>