<option type="enum" id="opt/largeformat-PageSize">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Page Size</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>A</arg_spot>
   <arg_substitution />
   <arg_proto>%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>dnj650c</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <driver>cdnj500</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 30</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 70</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 90</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 100</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 100plus</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 110</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 130</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 5000</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 5500</model>
      <driver>chp2200</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 3500CP</model>
      <driver>Postscript1</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
     <constraint sense="true">
      <make>HP</make>
      <model>DesignJet 5500ps</model>
      <driver>Postscript1</driver>
      <arg_defval>ev/largeformat-PageSize-Letter</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/largeformat-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> -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-Legal">
    <ev_longname>
     <en>US 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/largeformat-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> -dDEVICEWIDTHPOINTS=522 -dDEVICEHEIGHTPOINTS=756</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-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> -dDEVICEWIDTHPOINTS=792 -dDEVICEHEIGHTPOINTS=1224</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-TabloidExtra">
    <ev_longname>
     <en>Tabloid Extra</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>TabloidExtra</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=864 -dDEVICEHEIGHTPOINTS=1296</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-Ledger">
    <ev_longname>
     <en>Ledger</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Ledger</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=1224 -dDEVICEHEIGHTPOINTS=792</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-AnsiA">
    <ev_longname>
     <en>ANSI A</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>AnsiA</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/largeformat-PageSize-AnsiB">
    <ev_longname>
     <en>ANSI B</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>AnsiB</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=792 -dDEVICEHEIGHTPOINTS=1224</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-AnsiC">
    <ev_longname>
     <en>ANSI C</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>AnsiC</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=1224 -dDEVICEHEIGHTPOINTS=1584</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-AnsiD">
    <ev_longname>
     <en>ANSI D</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>AnsiD</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=1584 -dDEVICEHEIGHTPOINTS=2448</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-AnsiE">
    <ev_longname>
     <en>ANSI E</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>AnsiE</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=2448 -dDEVICEHEIGHTPOINTS=3168</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-SuperA">
    <ev_longname>
     <en>Super A</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>SuperA</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=644 -dDEVICEHEIGHTPOINTS=1008</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-SuperB">
    <ev_longname>
     <en>Super B</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>SuperB</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=936 -dDEVICEHEIGHTPOINTS=1368</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ArchA">
    <ev_longname>
     <en>Arch A</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ArchA</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=648 -dDEVICEHEIGHTPOINTS=864</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ArchB">
    <ev_longname>
     <en>Arch B</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ArchB</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=864 -dDEVICEHEIGHTPOINTS=1296</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ArchC">
    <ev_longname>
     <en>Arch C</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ArchC</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=1296 -dDEVICEHEIGHTPOINTS=1728</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ArchD">
    <ev_longname>
     <en>Arch D</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ArchD</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=1728 -dDEVICEHEIGHTPOINTS=2592</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ArchE">
    <ev_longname>
     <en>Arch E</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ArchE</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=2592 -dDEVICEHEIGHTPOINTS=3456</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-4A">
    <ev_longname>
     <en>4A</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>4A</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=4768 -dDEVICEHEIGHTPOINTS=6749</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-2A">
    <ev_longname>
     <en>2A</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>2A</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=3370 -dDEVICEHEIGHTPOINTS=4768</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-A0">
    <ev_longname>
     <en>A0</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>A0</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=2384 -dDEVICEHEIGHTPOINTS=3370</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-A1">
    <ev_longname>
     <en>A1</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>A1</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=1684 -dDEVICEHEIGHTPOINTS=2384</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-A2">
    <ev_longname>
     <en>A2</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>A2</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=1191 -dDEVICEHEIGHTPOINTS=1684</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-A3">
    <ev_longname>
     <en>A3</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>A3</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=842 -dDEVICEHEIGHTPOINTS=1191</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-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> -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-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> -dDEVICEWIDTHPOINTS=421 -dDEVICEHEIGHTPOINTS=595</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-RA0">
    <ev_longname>
     <en>RA0</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RA0</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=2437 -dDEVICEHEIGHTPOINTS=3458</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-RA1">
    <ev_longname>
     <en>RA1</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RA1</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=1729 -dDEVICEHEIGHTPOINTS=2437</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-RA2">
    <ev_longname>
     <en>RA2</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RA2</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=1218 -dDEVICEHEIGHTPOINTS=1729</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-RA3">
    <ev_longname>
     <en>RA3</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RA3</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=864 -dDEVICEHEIGHTPOINTS=1218</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-RA4">
    <ev_longname>
     <en>RA4</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RA4</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=609 -dDEVICEHEIGHTPOINTS=864</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-SRA0">
    <ev_longname>
     <en>SRA0</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>SRA0</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=2551 -dDEVICEHEIGHTPOINTS=3628</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-SRA1">
    <ev_longname>
     <en>SRA1</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>SRA1</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=1814 -dDEVICEHEIGHTPOINTS=2551</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-SRA2">
    <ev_longname>
     <en>SRA2</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>SRA2</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=1275 -dDEVICEHEIGHTPOINTS=1814</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-SRA3">
    <ev_longname>
     <en>SRA3</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>SRA3</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=907 -dDEVICEHEIGHTPOINTS=1275</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-SRA4">
    <ev_longname>
     <en>SRA4</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>SRA4</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=637 -dDEVICEHEIGHTPOINTS=907</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-JISB0">
    <ev_longname>
     <en>B0 (JIS)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>JISB0</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=2919 -dDEVICEHEIGHTPOINTS=4127</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-JISB1">
    <ev_longname>
     <en>B1 (JIS)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>JISB1</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=2063 -dDEVICEHEIGHTPOINTS=2919</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-JISB2">
    <ev_longname>
     <en>B2 (JIS)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>JISB2</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=1459 -dDEVICEHEIGHTPOINTS=2063</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-JISB3">
    <ev_longname>
     <en>B3 (JIS)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>JISB3</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=1029 -dDEVICEHEIGHTPOINTS=1459</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-JISB4">
    <ev_longname>
     <en>B4 (JIS)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>JISB4</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=727 -dDEVICEHEIGHTPOINTS=1029</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-JISB5">
    <ev_longname>
     <en>B5 (JIS)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>JISB5</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=518 -dDEVICEHEIGHTPOINTS=727</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ISOB0">
    <ev_longname>
     <en>B0 (ISO)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ISOB0</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=2834 -dDEVICEHEIGHTPOINTS=4008</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ISOB1">
    <ev_longname>
     <en>B1 (ISO)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ISOB1</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=2004 -dDEVICEHEIGHTPOINTS=2834</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ISOB2">
    <ev_longname>
     <en>B2 (ISO)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ISOB2</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=1417 -dDEVICEHEIGHTPOINTS=2004</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ISOB3">
    <ev_longname>
     <en>B3 (ISO)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ISOB3</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=1000 -dDEVICEHEIGHTPOINTS=1417</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ISOB4">
    <ev_longname>
     <en>B4 (ISO)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ISOB4</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=708 -dDEVICEHEIGHTPOINTS=1000</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-ISOB5">
    <ev_longname>
     <en>B5 (ISO)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ISOB5</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=498 -dDEVICEHEIGHTPOINTS=708</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-C0">
    <ev_longname>
     <en>C0</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>C0</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=2599 -dDEVICEHEIGHTPOINTS=3676</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-C1">
    <ev_longname>
     <en>C1</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>C1</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=1836 -dDEVICEHEIGHTPOINTS=2599</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-C2">
    <ev_longname>
     <en>C2</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>C2</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=1298 -dDEVICEHEIGHTPOINTS=1836</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-C3">
    <ev_longname>
     <en>C3</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>C3</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=918 -dDEVICEHEIGHTPOINTS=1298</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-C4">
    <ev_longname>
     <en>C4</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>C4</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=649 -dDEVICEHEIGHTPOINTS=918</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-C5">
    <ev_longname>
     <en>C5</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>C5</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/largeformat-PageSize-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/largeformat-PageSize-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/largeformat-PageSize-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/largeformat-PageSize-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/largeformat-PageSize-8x10">
    <ev_longname>
     <en>8x10</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>8x10</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=576 -dDEVICEHEIGHTPOINTS=720</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-8x12">
    <ev_longname>
     <en>8x12</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>8x12</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=576 -dDEVICEHEIGHTPOINTS=864</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-11x14">
    <ev_longname>
     <en>11x14</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>11x14</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=792 -dDEVICEHEIGHTPOINTS=1008</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-11x17">
    <ev_longname>
     <en>11x17</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>11x17</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=792 -dDEVICEHEIGHTPOINTS=1224</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-13x19">
    <ev_longname>
     <en>13x19</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>13x19</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=936 -dDEVICEHEIGHTPOINTS=1368</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-16x20">
    <ev_longname>
     <en>16x20</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>16x20</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=1152 -dDEVICEHEIGHTPOINTS=1440</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-PageSize-16x24">
    <ev_longname>
     <en>16x24</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>16x24</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=1152 -dDEVICEHEIGHTPOINTS=1728</ev_driverval>
   </enum_val>
   <enum_val id="ev/largeformat-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> -dDEVICEWIDTHPOINTS=0 -dDEVICEHEIGHTPOINTS=0</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
