<option type="enum" id="opt/pjxl-RenderType">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Rendering type</en>
  </arg_longname>
  <arg_shortname>
   <en>RenderType</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>General</arg_group>
   <arg_order>120</arg_order>
   <arg_spot>A</arg_spot>
   <arg_substitution />
   <arg_proto> -dRenderType=%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>pjxl</driver>
      <arg_defval>ev/pjxl-RenderType-Driver</arg_defval>
     </constraint>
     <constraint sense="true">
      <driver>pjxl300</driver>
      <arg_defval>ev/pjxl-RenderType-Driver</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/pjxl-RenderType-Driver">
    <ev_longname>
     <en>Driver does dithering</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Driver</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/pjxl-RenderType-SnapToPrimaries">
    <ev_longname>
     <en>Snap to primaries</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>SnapToPrimaries</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/pjxl-RenderType-BlackToWhite">
    <ev_longname>
     <en>Snap black to white, others to black</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>BlackToWhite</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/pjxl-RenderType-Ordered">
    <ev_longname>
     <en>Ordered dithering</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Ordered</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/pjxl-RenderType-ErrorDiffusion">
    <ev_longname>
     <en>Error diffusion</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ErrorDiffusion</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>4</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjxl-RenderType-OrderedMono">
    <ev_longname>
     <en>Monochrome ordered dithering</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>OrderedMono</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>5</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjxl-RenderType-ErrorDiffusionMono">
    <ev_longname>
     <en>Monochrome error diffusion</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ErrorDiffusionMono</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>6</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjxl-RenderType-Cluster">
    <ev_longname>
     <en>Cluster ordered dither</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Cluster</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>7</ev_driverval>
   </enum_val>
   <enum_val id="ev/pjxl-RenderType-ClusterMono">
    <ev_longname>
     <en>Monochrome cluster ordered dither</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>ClusterMono</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>8</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
