<option type="enum" id="opt/176">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Media Type</en>
  </arg_longname>
  <arg_shortname>
   <en>MediaType</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>General</arg_group>
   <arg_order>300</arg_order>
   <arg_spot>C</arg_spot>
   <arg_substitution />
   <arg_proto> -media %s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>ppmtocpva</driver>
      <arg_defval>ev/940</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/940">
    <ev_longname>
     <en>Plain Paper</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Paper</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>paper</ev_driverval>
   </enum_val>
   <enum_val id="ev/941">
    <ev_longname>
     <en>Iron-On Transfer Sheet</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>IronOn</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>iron-on</ev_driverval>
   </enum_val>
   <enum_val id="ev/942">
    <ev_longname>
     <en>Thick Paper</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Thick</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>thick</ev_driverval>
   </enum_val>
   <enum_val id="ev/943">
    <ev_longname>
     <en>Post Card</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Postcard</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>postcard</ev_driverval>
   </enum_val>
   <enum_val id="ev/944">
    <ev_longname>
     <en>High Grade Paper</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>HighGrade</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>highgrade</ev_driverval>
   </enum_val>
   <enum_val id="ev/945">
    <ev_longname>
     <en>Hot OHP Media</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>OHP</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>ohp</ev_driverval>
   </enum_val>
   <enum_val id="ev/946">
    <ev_longname>
     <en>Back Print Media</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>BackPrint</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>backprint</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
