<option type="enum" id="opt/bjc250gs-MediaType">
  <!-- 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>120</arg_order>
   <arg_spot>A</arg_spot>
   <arg_substitution />
   <arg_proto> -sMedia=%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="false">
      <driver>bjc250gs</driver>
      <arg_defval>ev/bjc250gs-MediaType-Plain</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/bjc250gs-MediaType-Plain">
    <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>Plain</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/bjc250gs-MediaType-Coated">
    <ev_longname>
     <en>Coated Paper</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Coated</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>CoatedPaper</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-Transparency">
    <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>Transparency</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/bjc250gs-MediaType-BackprintFilm">
    <ev_longname>
     <en>Backprint Film</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>BackprintFilm</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>BackprintFilm</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-PaperWithLead">
    <ev_longname>
     <en>Paper With Lead</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>PaperWithLead</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>PaperWithLead</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-Textile">
    <ev_longname>
     <en>Textile</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Textile</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Textile</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-Glossy">
    <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>Glossy</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/bjc250gs-MediaType-HighGlossyFilm">
    <ev_longname>
     <en>Highly Glossy Film</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>HighGlossyFilm</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>HighGlossyFilm</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-Envelope">
    <ev_longname>
     <en>Envelope</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Envelope</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Envelope</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-Card">
    <ev_longname>
     <en>Card</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Card</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Card</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-HiRes1">
    <ev_longname>
     <en>High Resolution Paper 1</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>HiRes1</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>HighResolutionPaper</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-HiRes2">
    <ev_longname>
     <en>High Resolution Paper 2</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>HiRes2</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>HighResPaper</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-FullBleed">
    <ev_longname>
     <en>Full Bleed</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>FullBleed</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>FullBleed</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-Banner">
    <ev_longname>
     <en>Banner</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Banner</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Banner</ev_driverval>
   </enum_val>
   <enum_val id="ev/bjc250gs-MediaType-Other">
    <ev_longname>
     <en>Other media type</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Other</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Other</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
