home *** CD-ROM | disk | FTP | other *** search
- <option type="enum" id="opt/eplaser-InputSlot">
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <arg_longname>
- <en>Paper Source</en>
- </arg_longname>
- <arg_shortname>
- <en>InputSlot</en><!-- backends only know <en> shortnames! -->
- </arg_shortname>
- <arg_execution>
- <arg_group>General</arg_group>
- <arg_order>100</arg_order>
- <arg_spot>A</arg_spot>
- <arg_substitution />
- <arg_proto> -dCasset=%s</arg_proto>
- </arg_execution>
- <constraints>
- <constraint sense="true">
- <driver>eplaser</driver>
- <arg_defval>ev/eplaser-InputSlot-Auto</arg_defval>
- </constraint>
- <constraint sense="true">
- <driver>eplaser-jp</driver>
- <arg_defval>ev/eplaser-InputSlot-Auto</arg_defval>
- </constraint>
- </constraints>
- <enum_vals>
- <enum_val id="ev/eplaser-InputSlot-Tray1">
- <ev_longname>
- <en>Tray 1</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray1</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/eplaser-InputSlot-Tray2">
- <ev_longname>
- <en>Tray 2</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray2</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/eplaser-InputSlot-Tray3">
- <ev_longname>
- <en>Tray 3</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray3</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/eplaser-InputSlot-Tray4">
- <ev_longname>
- <en>Tray 4</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray4</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/eplaser-InputSlot-Tray5">
- <ev_longname>
- <en>Tray 5</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray5</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/eplaser-InputSlot-Tray6">
- <ev_longname>
- <en>Tray 6</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray6</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/eplaser-InputSlot-Tray7">
- <ev_longname>
- <en>Tray 7</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray7</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/eplaser-InputSlot-Tray8">
- <ev_longname>
- <en>Tray 8</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray8</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_val id="ev/eplaser-InputSlot-Tray9">
- <ev_longname>
- <en>Tray 9</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray9</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_val id="ev/eplaser-InputSlot-Tray10">
- <ev_longname>
- <en>Tray 10</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray10</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>10</ev_driverval>
- </enum_val>
- <enum_val id="ev/eplaser-InputSlot-Tray11">
- <ev_longname>
- <en>Tray 11</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray11</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>11</ev_driverval>
- </enum_val>
- <enum_val id="ev/eplaser-InputSlot-Tray12">
- <ev_longname>
- <en>Tray 12</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray12</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>12</ev_driverval>
- </enum_val>
- <enum_val id="ev/eplaser-InputSlot-Tray13">
- <ev_longname>
- <en>Tray 13</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray13</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>13</ev_driverval>
- </enum_val>
- <enum_val id="ev/eplaser-InputSlot-Tray14">
- <ev_longname>
- <en>Tray 14</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray14</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>14</ev_driverval>
- </enum_val>
- <enum_val id="ev/eplaser-InputSlot-Tray15">
- <ev_longname>
- <en>Tray 15</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Tray15</en>
- <!-- Until someone tells me how to learn the user locale in
- backends, the shortname must be monolingual in <en>! -->
- </ev_shortname>
- <ev_driverval>15</ev_driverval>
- </enum_val>
- <enum_val id="ev/eplaser-InputSlot-Auto">
- <ev_longname>
- <en>Auto Selection</en>
- </ev_longname>
- <!-- A multilingual <comments> block can appear here, too;
- it should be treated as documentation for the user. -->
- <ev_shortname>
- <en>Auto</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_vals>
- </option>
-