<option type="enum" id="opt/ppmtomd-ColorMode">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Color Mode</en>
  </arg_longname>
  <arg_shortname>
   <en>ColorMode</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>General</arg_group>
   <arg_order>130</arg_order>
   <arg_spot>C</arg_spot>
   <arg_substitution />
   <arg_proto> -datamode %s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>ppmtomd</driver>
      <arg_defval>ev/ppmtomd-ColorMode-Colour</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/ppmtomd-ColorMode-Colour">
    <ev_longname>
     <en>Colours one page at a time</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Colour</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Colour</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-ColorMode-Cassette">
    <ev_longname>
     <en>Do not care about cartridges, colours one page at a time</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Cassette</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Cassette</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-ColorMode-RasterColour">
    <ev_longname>
     <en>Each line in all colours</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RasterColour</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>RasterColour</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-ColorMode-RasterCassette">
    <ev_longname>
     <en>Do not care about cartridges, each line in all colours</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RasterCassette</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>RasterCassette</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-ColorMode-NColour">
    <ev_longname>
     <en>More than 4 colours, colours one page at a time</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>NColour</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>NColour</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-ColorMode-Black">
    <ev_longname>
     <en>Monochrome printing, standard black cartridge</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Black</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Black</ev_driverval>
   </enum_val>
   <enum_val id="ev/ppmtomd-ColorMode-EconoBlack">
    <ev_longname>
     <en>Monochrome printing, re-usable economy black cartridge</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>EconoBlack</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>EconoBlack</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
