<option type="enum" id="opt/8">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Compression Method</en>
  </arg_longname>
  <arg_shortname>
   <en>CompressionMethod</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>Miscellaneous</arg_group>
   <arg_order>100</arg_order>
   <arg_spot>A</arg_spot>
   <arg_substitution />
   <arg_proto> -dCompressionMethod=%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="false">
      <driver>pcl3</driver>
      <arg_defval>ev/145</arg_defval>
     </constraint>
     <constraint sense="true">
      <driver>hpdj</driver>
      <arg_defval>ev/145</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/141">
    <ev_longname>
     <en>Unencoded</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Unencoded</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>0</ev_driverval>
   </enum_val>
   <enum_val id="ev/142">
    <ev_longname>
     <en>Runlength Encoding</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>RLE</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>1</ev_driverval>
   </enum_val>
   <enum_val id="ev/143">
    <ev_longname>
     <en>Tagged Image File Format</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>TIFF</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>2</ev_driverval>
   </enum_val>
   <enum_val id="ev/144">
    <ev_longname>
     <en>Delta Row Compression</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>DRC</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>3</ev_driverval>
   </enum_val>
   <enum_val id="ev/145">
    <ev_longname>
     <en>Compressed Replacement Delta Row Encoding</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>CRDRE</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>9</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
