<option type="enum" id="opt/gdi-RET">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>RET (Resolution Enhancement)</en>
  </arg_longname>
  <arg_shortname>
   <en>RET</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>General</arg_group>
   <arg_order>140</arg_order>
   <arg_spot>E</arg_spot>
   <arg_substitution />
   <arg_proto>s/(\@PJL ENTER LANGUAGE)/\@PJL SET RET = %s\r\n$1/; </arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>gdi</driver>
      <arg_defval>ev/gdi-RET-Off</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/gdi-RET-On">
    <ev_longname>
     <en>On</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>On</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>ON</ev_driverval>
    <constraints>
     <constraint sense="false">
      <driver>gdi</driver>
     </constraint>
    </constraints>
   </enum_val>
   <enum_val id="ev/gdi-RET-Off">
    <ev_longname>
     <en>Off</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Off</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval>OFF</ev_driverval>
   </enum_val>
  </enum_vals>
</option>
