<option type="enum" id="opt/min12xxw-GSPageSize">
  <!-- 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>GSPageSize</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>%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>min12xxw</driver>
      <arg_defval>ev/min12xxw-GSPageSize-Letter</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=1008</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=595</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=283 -dDEVICEHEIGHTPOINTS=420</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=420 -dDEVICEHEIGHTPOINTS=567</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=278 -dDEVICEHEIGHTPOINTS=539</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=340 -dDEVICEHEIGHTPOINTS=666</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=524 -dDEVICEHEIGHTPOINTS=737</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=369 -dDEVICEHEIGHTPOINTS=524</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=936</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=756</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=522 -dDEVICEHEIGHTPOINTS=756</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=396 -dDEVICEHEIGHTPOINTS=612</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=279 -dDEVICEHEIGHTPOINTS=540</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=297 -dDEVICEHEIGHTPOINTS=684</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=312 -dDEVICEHEIGHTPOINTS=624</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=459 -dDEVICEHEIGHTPOINTS=649</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=323 -dDEVICEHEIGHTPOINTS=459</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=499 -dDEVICEHEIGHTPOINTS=709</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=340 -dDEVICEHEIGHTPOINTS=666</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=255 -dDEVICEHEIGHTPOINTS=581</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=261 -dDEVICEHEIGHTPOINTS=468</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=936</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=340 -dDEVICEHEIGHTPOINTS=499</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=298 -dDEVICEHEIGHTPOINTS=666</ev_driverval>
   </enum_val>
   <enum_val id="ev/min12xxw-GSPageSize-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> -dDEVICEWIDTHPOINTS=567 -dDEVICEHEIGHTPOINTS=839</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
