<option type="enum" id="opt/sipixa6.upp-PageSize">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Page Size (Input paper size, will be scaled to A6)</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>E</arg_spot>
   <arg_required />
   <arg_substitution />
   <arg_proto>%s</arg_proto>
  </arg_execution>
  <constraints>
   <constraint sense="true">
    <driver>sipixa6.upp</driver>
    <arg_defval>ev/sipixa6.upp-PageSize-Letter</arg_defval>
   </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/sipixa6.upp-PageSize-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> -Pa4</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-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> -Pa5</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-A6">
    <ev_longname>
     <en>A6</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>A6</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -W10.5cm -H14.8cm</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-Letter">
    <ev_longname>
     <en>US 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> -Pletter</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-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> -Plegal</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-Tabloid">
    <ev_longname>
     <en>Tabloid</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Tabloid</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -Ptabloid</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-Statement">
    <ev_longname>
     <en>Statement</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Statement</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -Pstatement</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-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> -Pexecutive</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-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> -Pfolio</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-10x14">
    <ev_longname>
     <en>10x14</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>10x14</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -P10x14</ev_driverval>
   </enum_val>
   <enum_val id="ev/sipixa6.upp-PageSize-Custom">
    <ev_longname>
     <en>Custom Size</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Custom</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -W%0 -H%1</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
