File: 122.xml

package info (click to toggle)
foomatic-db 20050420-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 12,100 kB
  • ctags: 3
  • sloc: xml: 169,666; sh: 153; makefile: 107
file content (90 lines) | stat: -rwxr-xr-x 2,987 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
<option type="enum" id="opt/122">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Darkness</en>
  </arg_longname>
  <arg_shortname>
   <en>Darkness</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>Adjustment</arg_group>
   <arg_order>100</arg_order>
   <arg_spot>A</arg_spot>
   <arg_substitution />
   <arg_proto>%FAKEOKI DARKNESS=%s\n</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>oki4drv</driver>
      <arg_defval>ev/789</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/787">
    <ev_longname>
     <en>Darkest</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Darkest</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/788">
    <ev_longname>
     <en>Dark</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Dark</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/789">
    <ev_longname>
     <en>Normal</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Normal</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/790">
    <ev_longname>
     <en>Light</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Light</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/791">
    <ev_longname>
     <en>Lightest</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Lightest</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_vals>
</option>