<option type="enum" id="opt/gdi-Density">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Toner Density</en>
  </arg_longname>
  <arg_shortname>
   <en>Density</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>Adjustment</arg_group>
   <arg_order>130</arg_order>
   <arg_spot>E</arg_spot>
   <arg_substitution />
   <arg_proto>s/PJL SET DENSITY = 1/PJL SET DENSITY = %s/; </arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>gdi</driver>
      <arg_defval>ev/gdi-Density-3</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/gdi-Density-1">
    <ev_longname>
     <en>1</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>1</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>1</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-Density-2">
    <ev_longname>
     <en>2</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>2</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>2</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-Density-3">
    <ev_longname>
     <en>3</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>3</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>3</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-Density-4">
    <ev_longname>
     <en>4</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>4</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>4</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-Density-5">
    <ev_longname>
     <en>5</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>5</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>5</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
