<option type="enum" id="opt/19">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Dithering Algorithm</en>
  </arg_longname>
  <arg_shortname>
   <en>Dither</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_postscript />
   <arg_proto>&lt;&lt;/Dither(%s)&gt;&gt;setpagedevice</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>stp</driver>
      <arg_defval>ev/239</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/240">
    <ev_longname>
     <en>Ordered</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Ordered</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Ordered</ev_driverval>
   </enum_val>
   <enum_val id="ev/241">
    <ev_longname>
     <en>Adaptive Random</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>AdaptiveRandom</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Adaptive Random</ev_driverval>
   </enum_val>
   <enum_val id="ev/242">
    <ev_longname>
     <en>Hybrid Floyd-Steinberg</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>HybridFloydSteinberg</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Hybrid Floyd-Steinberg</ev_driverval>
   </enum_val>
   <enum_val id="ev/243">
    <ev_longname>
     <en>Random Floyd-Steinberg</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RandomFloydSteinberg</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Random Floyd-Steinberg</ev_driverval>
   </enum_val>
   <enum_val id="ev/239">
    <ev_longname>
     <en>Adaptive Hybrid</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>AdaptiveHybrid</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Adaptive Hybrid</ev_driverval>
   </enum_val>
   <enum_val id="ev/369">
    <ev_longname>
     <en>Fast</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Fast</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Fast</ev_driverval>
   </enum_val>
   <enum_val id="ev/599">
    <ev_longname>
     <en>Very Fast</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>VeryFast</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Very Fast</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
