<option type="enum" id="opt/pjl-Samsung-ML-1650-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>100</arg_order>
   <arg_spot>A</arg_spot>
   <arg_pjl />
   <arg_proto>SET PAPERTYPE=%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <make>Samsung</make>
      <model>ML-1650</model>
      <arg_defval>ev/pjl-Samsung-ML-1650-Default</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>Samsung</make>
      <model>ML-1651N</model>
      <arg_defval>ev/pjl-Samsung-ML-1650-Default</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
      <enum_val id="ev/pjl-Samsung-ML-1650-Default">
    <ev_longname>
     <en>Printer default</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Default</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>OFF</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjl-Samsung-ML-1650-Normal">
    <ev_longname>
     <en>Normal</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Normal</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>NORMAL</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjl-Samsung-ML-1650-Bond">
    <ev_longname>
     <en>Bond</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Bond</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>BOND</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjl-Samsung-ML-1650-Transparency">
    <ev_longname>
     <en>Transparency</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>OHP</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjl-Samsung-ML-1650-Card">
    <ev_longname>
     <en>Card Stock</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/pjl-Samsung-ML-1650-Labels">
    <ev_longname>
     <en>Adhesive Labels</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Labels</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>LABEL</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjl-Samsung-ML-1650-Preprinted">
    <ev_longname>
     <en>Pre-printed paper</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Preprinted</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>USED</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjl-Samsung-ML-1650-Colored">
    <ev_longname>
     <en>Colored Paper</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Colored</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>COLOR</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjl-Samsung-ML-1650-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>ENV</ev_driverval>
   </enum_val>

  </enum_vals>
</option>
