<option type="enum" id="opt/pbmtozjs-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> -g%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense='true'>
      <driver>pbmtozjs</driver>
      <arg_defval>ev/pbmtozjs-PageSize-Letter</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/pbmtozjs-PageSize-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>4875x6400</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-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>4875x8200</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-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>4125x6100</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-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>4736x6817</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-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>3283x4736</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-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>2250x3300</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-PageSize-4x6">
    <ev_longname>
     <en>Index card 4x6</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>4x6</en>
     <!-- Until someone tells me how to learn the user locale in
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>2175x3400</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-PageSize-3x5">
    <ev_longname>
     <en>Index card 3x5</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>3x5</en>
     <!-- Until someone tells me how to learn the user locale in
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>1575x2800</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-PageSize-B5JIS">
    <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>B5JIS</en>
     <!-- Until someone tells me how to learn the user locale in
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>4075x5875</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-PageSize-Oufuku">
    <ev_longname>
     <en>Oufuku-Hagaki</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>3275x4525</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-PageSize-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>2133x3300</ev_driverval>
   </enum_val>
   <enum_val id="ev/pbmtozjs-PageSize-FLSA">
    <ev_longname>
     <en>American Foolscap</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>FLSA</en>
     <!-- Until someone tells me how to learn the user locale in
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>4875x7600</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
