<option type="enum" id="opt/144">
  <!-- 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>150</arg_order>
   <arg_spot>A</arg_spot>
   <arg_substitution />
   <arg_proto> -sMediaType=%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>md5k</driver>
      <arg_defval>ev/869</arg_defval>
     </constraint>
     <constraint sense="true">
      <driver>md2k</driver>
      <arg_defval>ev/869</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/873">
    <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/874">
    <ev_longname>
     <en>Fine Paper</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>FinePaper</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>FinePaper</ev_driverval>
   </enum_val>
   <enum_val id="ev/875">
    <ev_longname>
     <en>Coated Film</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CoatedFilm</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>CoatedFilm</ev_driverval>
   </enum_val>
   <enum_val id="ev/876">
    <ev_longname>
     <en>Glossy Paper</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>GlossyPaper</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>GlossyPaper</ev_driverval>
   </enum_val>
   <enum_val id="ev/877">
    <ev_longname>
     <en>Transparency Film</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>TransparencyFilm</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>TransparencyFilm</ev_driverval>
   </enum_val>
   <enum_val id="ev/878">
    <ev_longname>
     <en>OHP</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/879">
    <ev_longname>
     <en>OHP (MD 2000)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>OHP_MD2000</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_MD2000</ev_driverval>
   </enum_val>
   <enum_val id="ev/869">
    <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>PlainPaper</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>PlainPaper</ev_driverval>
   </enum_val>
   <enum_val id="ev/870">
    <ev_longname>
     <en>Iron Seal</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>IronSeal</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>IronSeal</ev_driverval>
   </enum_val>
   <enum_val id="ev/871">
    <ev_longname>
     <en>Rebeca Free</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RebecaFree</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>RebecaFree</ev_driverval>
   </enum_val>
   <enum_val id="ev/872">
    <ev_longname>
     <en>Cardboard</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CardBoard</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>CardBoard</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
