<option type="enum" id="opt/ppmtomd-PrintColors">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Colours to be printed</en>
  </arg_longname>
  <arg_shortname>
   <en>PrintColors</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>Miscellaneous</arg_group>
   <arg_order>120</arg_order>
   <arg_spot>C</arg_spot>
   <arg_substitution />
   <arg_proto> -colours %s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>ppmtomd</driver>
      <arg_defval>ev/ppmtomd-PrintColors-CMYK</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/ppmtomd-PrintColors-None">
    <ev_longname>
     <en>None</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>None</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>none</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-K">
    <ev_longname>
     <en>Black only</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>K</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>k</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-C">
    <ev_longname>
     <en>Cyan only</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>C</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>c</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-M">
    <ev_longname>
     <en>Magenta only</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>M</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>m</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-Y">
    <ev_longname>
     <en>Yellow only</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Y</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>y</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-CK">
    <ev_longname>
     <en>Cyan, Black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CK</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>c,k</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-CM">
    <ev_longname>
     <en>Magenta, Black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>MK</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>m,k</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-YK">
    <ev_longname>
     <en>Yellow, Black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>YK</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>y,k</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-CM">
    <ev_longname>
     <en>Cyan, Magenta</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CM</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>c,m</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-CY">
    <ev_longname>
     <en>Cyan, Yellow</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CY</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>c,y</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-MY">
    <ev_longname>
     <en>Magenta, Yellow</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>MY</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>m,y</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-CMK">
    <ev_longname>
     <en>Cyan, Magenta, Black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CMK</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>c,m,k</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-CYK">
    <ev_longname>
     <en>Cyan, Yellow, Black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CYK</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>c,y,k</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-MYK">
    <ev_longname>
     <en>Magenta, Yellow, Black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>MYK</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>m,y,k</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-CMY">
    <ev_longname>
     <en>Cyan, Magenta, Yellow</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CMY</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>c,m,y</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-PrintColors-CMYK">
    <ev_longname>
     <en>Cyan, Magenta, Yellow, Black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CMYK</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>c,m,y,k</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
