|
Server : Apache/2.2.2 (Fedora) System : Linux App1.pathumtani.go.th 2.6.20-1.2320.fc5smp #1 SMP Tue Jun 12 19:40:16 EDT 2007 i686 User : apache ( 48) PHP Version : 5.2.9 Disable Function : NONE Directory : /usr/share/foomatic/db/source/opt/ |
Upload File : |
<option type="enum" id="opt/129">
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<arg_longname>
<en>Colours to be used</en>
</arg_longname>
<arg_shortname>
<en>PrintColors</en><!-- backends only know <en> shortnames! -->
</arg_shortname>
<arg_execution>
<arg_group>Miscellaneous</arg_group>
<arg_order>100</arg_order>
<arg_spot>Z</arg_spot>
<arg_postscript />
<arg_proto><</PrintColors %s>>setpagedevice</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>bjc800</driver>
<arg_defval>ev/838</arg_defval>
</constraint>
<constraint sense="true">
<driver>bjc600</driver>
<arg_defval>ev/838</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/823">
<ev_longname>
<en>Black for any colour</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>KKKK</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/824">
<ev_longname>
<en>Cyan only</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>C</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/825">
<ev_longname>
<en>Magenta only</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>M</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/826">
<ev_longname>
<en>Cyan, Magenta</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CM</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/827">
<ev_longname>
<en>Yellow only</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>Y</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/828">
<ev_longname>
<en>Cyan, Yellow</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CY</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/829">
<ev_longname>
<en>Magenta, Yellow</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>MY</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/830">
<ev_longname>
<en>Cyan, Magenta, Yellow</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CMY</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/831">
<ev_longname>
<en>Black only</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>K</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/832">
<ev_longname>
<en>Cyan, Black</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CK</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/833">
<ev_longname>
<en>Magenta, Black</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>MK</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/834">
<ev_longname>
<en>Cyan, Magenta, Black</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CMK</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/835">
<ev_longname>
<en>Yellow, Black</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>YK</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/836">
<ev_longname>
<en>Cyan, Yellow, Black</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CYK</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/837">
<ev_longname>
<en>Magenta, Yellow, Black</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>MYK</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/838">
<ev_longname>
<en>Cyan, Magenta, Yellow, Black</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>CMYK</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_vals>
</option>