<option type="enum" id="opt/min12xxw-DriverPageSize">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Driver Page Size</en>
  </arg_longname>
  <arg_shortname>
   <en>DriverPageSize</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>General</arg_group>
   <arg_order>100</arg_order>
   <arg_spot>B</arg_spot>
   <arg_substitution />
   <arg_proto> -f %s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>min12xxw</driver>
      <arg_defval>ev/min12xxw-DriverPageSize-Letter</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/min12xxw-DriverPageSize-Letter">
    <ev_longname>
     <en>Letter</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Letter</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>letter</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-Legal">
    <ev_longname>
     <en>Legal</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Legal</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>legal</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-A4">
    <ev_longname>
     <en>A4</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>A4</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>a4</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-A5">
    <ev_longname>
     <en>A5</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>A5</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>a5</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-Hagaki">
    <ev_longname>
     <en>Hagaki</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Hagaki</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>jpost</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-Oufuku">
    <ev_longname>
     <en>Oufuku</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Oufuku</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>corpost</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w278h539">
    <ev_longname>
     <en>JIS Yokei 6-gou</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w278h539</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>jisy6</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w340h666">
    <ev_longname>
     <en>JIS Yokei 0-gou</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w340h666</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>jisy0</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w524h737">
    <ev_longname>
     <en>Chinese 16K</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w524h737</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>chinese16k</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w369h524">
    <ev_longname>
     <en>Chinese 32K</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w369h524</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>chinese32k</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w612h936">
    <ev_longname>
     <en>G. Legal</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w612h936</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>glegal</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w612h756">
    <ev_longname>
     <en>G. Letter</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w612h756</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>gletter</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-Executive">
    <ev_longname>
     <en>Executive</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Executive</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>executive</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-HalfLetter">
    <ev_longname>
     <en>Half Letter</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>HalfLetter</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>halfletter</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-EnvMonarch">
    <ev_longname>
     <en>Envelope Monarch</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>EnvMonarch</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>envmonarch</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-Env10">
    <ev_longname>
     <en>Envelope #10</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Env10</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>env10</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-EnvDL">
    <ev_longname>
     <en>Envelope DL</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>EnvDL</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>envdl</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-EnvC5">
    <ev_longname>
     <en>Envelope C5</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>EnvC5</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>envc5</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-EnvC6">
    <ev_longname>
     <en>Envelope C6</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>EnvC6</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>envc6</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-EnvISOB5">
    <ev_longname>
     <en>Envelope B5</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>EnvISOB5</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>envb5</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w340h666">
    <ev_longname>
     <en>Choukei-3Gou</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w340h666</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Choukei-3Gou</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w255h581">
    <ev_longname>
     <en>Choukei-4Gou</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w255h581</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>Choukei-4Gou</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w261h468">
    <ev_longname>
     <en>Envelope 6 1/2</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w261h468</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>envb6</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-Folio">
    <ev_longname>
     <en>Folio</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Folio</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>folio</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w340h499">
    <ev_longname>
     <en>JIS Yokei 1-gou</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w340h499</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>jisy1</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w298h666">
    <ev_longname>
     <en>JIS Yokei 2-gou</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w298h666</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>jisy2</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-DriverPageSize-w567h839">
    <ev_longname>
     <en>Quad postcard</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>w567h839</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>quadpost</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
