<option type="enum" id="opt/128">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Media Weight</en>
  </arg_longname>
  <arg_shortname>
   <en>MediaWeight</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>General</arg_group>
   <arg_order>100</arg_order>
   <arg_spot>Z</arg_spot>
   <arg_postscript />
   <arg_proto>&lt;&lt;/MediaWeight %s&gt;&gt;setpagedevice</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>bjc800</driver>
      <arg_defval>ev/819</arg_defval>
     </constraint>
     <constraint sense="true">
      <driver>bjc600</driver>
      <arg_defval>ev/819</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/819">
    <ev_longname>
     <en>Normal paper</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>80</ev_driverval>
   </enum_val>
   <enum_val id="ev/820">
    <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>150</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
