<option type="enum" id="opt/76">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Resolution</en>
  </arg_longname>
  <arg_shortname>
   <en>Resolution</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_substitution />
   <arg_proto> -r%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>lex5700</driver>
      <arg_defval>ev/625</arg_defval>
     </constraint>
     <constraint sense="true">
      <driver>lex7000</driver>
      <arg_defval>ev/625</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/623">
    <ev_longname>
     <en>300x300 dpi</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>300x300dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>300x300</ev_driverval>
   </enum_val>
   <enum_val id="ev/624">
    <ev_longname>
     <en>300x600 dpi</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>300x600dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>300x600</ev_driverval>
   </enum_val>
   <enum_val id="ev/625">
    <ev_longname>
     <en>600x600 dpi</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>600x600dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>600x600</ev_driverval>
   </enum_val>
   <enum_val id="ev/626">
    <ev_longname>
     <en>600x1200 dpi</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>600x1200dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>600x1200</ev_driverval>
   </enum_val>
   <enum_val id="ev/627">
    <ev_longname>
     <en>1200x1200 dpi</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>1200x1200dpi</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>1200x1200</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
