<option type="enum" id="opt/113">
  <!-- A multilingual <comments> block can appear here, too;
       it should be treated as documentation for the user. -->
  <arg_longname>
   <en>Device</en>
  </arg_longname>
  <arg_shortname>
   <en>Device</en><!-- backends only know <en> shortnames! -->
  </arg_shortname>
  <arg_execution>
   <arg_group>Miscellaneous</arg_group>
   <arg_order>100</arg_order>
   <arg_spot>F</arg_spot>
   <arg_required />
   <arg_substitution />
   <arg_proto>%s</arg_proto>
  </arg_execution>
  <constraints>
     <constraint sense="true">
      <driver>lpstyl</driver>
      <arg_defval>ev/754</arg_defval>
     </constraint>
  </constraints>
  <enum_vals>
   <enum_val id="ev/750">
    <ev_longname>
     <en>Serial Port #1 (Linux)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>LinuxSerial1</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -f /dev/ttyS0</ev_driverval>
   </enum_val>
   <enum_val id="ev/751">
    <ev_longname>
     <en>Serial Port #2 (Linux)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>LinuxSerial2</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -f /dev/ttyS1</ev_driverval>
   </enum_val>
   <enum_val id="ev/752">
    <ev_longname>
     <en>Serial Port #1 (NetBSD)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>NetBSDSerial1</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -f /dev/tty01</ev_driverval>
   </enum_val>
   <enum_val id="ev/753">
    <ev_longname>
     <en>Serial Port #2 (NetBSD)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>NetBSDSerial2</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -f /dev/tty02</ev_driverval>
   </enum_val>
   <enum_val id="ev/749">
    <ev_longname>
     <en>Link stylewriter in dev directory (set it to the appropriate device)</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>DefaultLink</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval> -f /dev/stylewriter</ev_driverval>
   </enum_val>
   <enum_val id="ev/754">
    <ev_longname>
     <en>Pass output to device set by the spooler</en>
    </ev_longname>
    <!-- A multilingual <comments> block can appear here, too;
         it should be treated as documentation for the user. -->
    <ev_shortname>
     <en>Spooler</en>
     <!-- Until someone tells me how to learn the user locale in 
          backends, the shortname must be monolingual in <en>! -->
    </ev_shortname>
    <ev_driverval></ev_driverval>
   </enum_val>
  </enum_vals>
</option>
