<option type="enum" id="opt/165">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Page Size and Printing Quality</en>
  </arg_longname>
  <arg_shortname>
   <en>PageSize</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_required />
   <arg_substitution />
   <arg_proto>%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>ppmtocpva</driver>
      <arg_defval>ev/930</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/935">
    <ev_longname>
     <en>Legal, 1200x600 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>LegalHR</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -sPAPERSIZE=legal -r1200x600 - | ppmtocpva -highres -highresinput -papersize legal</ev_driverval>
   </enum_val>
   <enum_val id="ev/938">
    <ev_longname>
     <en>B5, 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>B5</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -sPAPERSIZE=b5 -r600x600 - | ppmtocpva -papersize b5</ev_driverval>
   </enum_val>
   <enum_val id="ev/939">
    <ev_longname>
     <en>B5, 1200x600 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>B5HR</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -sPAPERSIZE=b5 -r1200x600 - | ppmtocpva -highres -highresinput -papersize b5</ev_driverval>
   </enum_val>
   <enum_val id="ev/930">
    <ev_longname>
     <en>Letter, 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>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> -sPAPERSIZE=letter -r600x600 - | ppmtocpva -papersize letter</ev_driverval>
   </enum_val>
   <enum_val id="ev/931">
    <ev_longname>
     <en>Letter, 1200x600 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>LetterHR</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -sPAPERSIZE=letter -r1200x600 - | ppmtocpva -highres -highresinput -papersize letter</ev_driverval>
   </enum_val>
   <enum_val id="ev/932">
    <ev_longname>
     <en>A4, 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>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> -sPAPERSIZE=a4 -r600x600 - | ppmtocpva -papersize a4</ev_driverval>
   </enum_val>
   <enum_val id="ev/933">
    <ev_longname>
     <en>A4, 1200x600 DPI</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>A4HR</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -sPAPERSIZE=a4 -r1200x600 - | ppmtocpva -highres -highresinput -papersize a4</ev_driverval>
   </enum_val>
   <enum_val id="ev/934">
    <ev_longname>
     <en>Legal, 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>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> -sPAPERSIZE=legal -r600x600 - | ppmtocpva -papersize legal</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
