<option type="enum" id="opt/215">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Black Levels</en>
  </arg_longname>
  <arg_shortname>
   <en>BlackLevels</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>Miscellaneous</arg_group>
   <arg_order>170</arg_order>
   <arg_spot>A</arg_spot>
   <arg_substitution />
   <arg_proto>%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>pcl3</driver>
      <arg_defval>ev/1071</arg_defval>
     </constraint>
     <constraint sense="false">
      <make>HP</make>
      <model>DeskJet 520</model>
      <driver>pcl3</driver>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/1051">
    <ev_longname>
     <en>4 Levels</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>4</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -dBlackLevels=4</ev_driverval>
   </enum_val>
   <enum_val id="ev/1049">
    <ev_longname>
     <en>2 Levels</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>2</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -dBlackLevels=2</ev_driverval>
   </enum_val>
   <enum_val id="ev/1050">
    <ev_longname>
     <en>3 Levels</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>3</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -dBlackLevels=3</ev_driverval>
   </enum_val>
   <enum_val id="ev/1052">
    <ev_longname>
     <en>No Black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>NoBlack</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -dBlackLevels=0</ev_driverval>
   </enum_val>
   <enum_val id="ev/1071">
    <ev_longname>
     <en>Default Setting</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Default</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval></ev_driverval>
   </enum_val>
  </enum_vals>
</option>
