<option type="enum" id="opt/gdi-PageSizeJCL">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Page Size (JCL)</en>
  </arg_longname>
  <arg_shortname>
   <en>PageSizeJCL</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_substitution />
   <arg_proto>s/PJL PAGE LETTER/PJL PAGE %s/; </arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>gdi</driver>
      <arg_defval>ev/gdi-PageSizeJCL-Letter</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/gdi-PageSizeJCL-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>LETTER</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>LEGAL</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>EXECUTIVE</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>A4</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>A5</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>A6</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>FOLIO</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>JISB5</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>COM10</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>MONARCH</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>DL</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>C5</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-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>C6</ev_driverval>
   </enum_val>
   <enum_val id="ev/gdi-PageSizeJCL-EnvB5">
    <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>EnvB5</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>B5</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
