|
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/96">
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<arg_longname>
<en>Resolution, Media Type</en>
</arg_longname>
<arg_shortname>
<en>Quality</en><!-- backends only know <en> shortnames! -->
</arg_shortname>
<arg_execution>
<arg_group>General</arg_group>
<arg_order>100</arg_order>
<arg_spot>B</arg_spot>
<arg_required />
<arg_substitution />
<arg_proto>@bjc610%s.upp</arg_proto>
</arg_execution>
<constraints>
<constraint sense="true">
<driver>bjc610a0.upp</driver>
<arg_defval>ev/707</arg_defval>
</constraint>
</constraints>
<enum_vals>
<enum_val id="ev/706">
<ev_longname>
<en>360x360dpi, plain paper, high speed</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360PlainFast</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a0</ev_driverval>
</enum_val>
<enum_val id="ev/707">
<ev_longname>
<en>360x360dpi, plain paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360Plain</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a1</ev_driverval>
</enum_val>
<enum_val id="ev/708">
<ev_longname>
<en>360x360dpi, coated paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360Coated</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a2</ev_driverval>
</enum_val>
<enum_val id="ev/709">
<ev_longname>
<en>360x360dpi, transparency film</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360Transparency</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a3</ev_driverval>
</enum_val>
<enum_val id="ev/710">
<ev_longname>
<en>360x360dpi, back print film</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360Backprint</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a4</ev_driverval>
</enum_val>
<enum_val id="ev/711">
<ev_longname>
<en>360x360dpi, fabric sheet</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360Fabric</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a5</ev_driverval>
</enum_val>
<enum_val id="ev/712">
<ev_longname>
<en>360x360dpi, glossy paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360Glossy</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a6</ev_driverval>
</enum_val>
<enum_val id="ev/713">
<ev_longname>
<en>360x360dpi, high gloss film</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360HighGloss</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a7</ev_driverval>
</enum_val>
<enum_val id="ev/714">
<ev_longname>
<en>360x360dpi, high resolution paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>360HighRes</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>a8</ev_driverval>
</enum_val>
<enum_val id="ev/715">
<ev_longname>
<en>720x720dpi, plain paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>720Plain</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>b1</ev_driverval>
<constraints>
<constraint sense="false">
<make>Canon</make>
<model>BJC-2100</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-600</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-250</model>
<arg_defval>na</arg_defval>
</constraint>
</constraints>
</enum_val>
<enum_val id="ev/716">
<ev_longname>
<en>720x720dpi, coated paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>720Coated</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>b2</ev_driverval>
<constraints>
<constraint sense="false">
<make>Canon</make>
<model>BJC-2100</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-600</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-250</model>
<arg_defval>na</arg_defval>
</constraint>
</constraints>
</enum_val>
<enum_val id="ev/717">
<ev_longname>
<en>720x720dpi, transparency film</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>720Transparency</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>b3</ev_driverval>
<constraints>
<constraint sense="false">
<make>Canon</make>
<model>BJC-250</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-2100</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-600</model>
<arg_defval>na</arg_defval>
</constraint>
</constraints>
</enum_val>
<enum_val id="ev/718">
<ev_longname>
<en>720x720dpi, back print film</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>720Backprint</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>b4</ev_driverval>
<constraints>
<constraint sense="false">
<make>Canon</make>
<model>BJC-2100</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-600</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-250</model>
<arg_defval>na</arg_defval>
</constraint>
</constraints>
</enum_val>
<enum_val id="ev/719">
<ev_longname>
<en>720x720dpi, glossy paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>720Glossy</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>b6</ev_driverval>
<constraints>
<constraint sense="false">
<make>Canon</make>
<model>BJC-2100</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-600</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-250</model>
<arg_defval>na</arg_defval>
</constraint>
</constraints>
</enum_val>
<enum_val id="ev/720">
<ev_longname>
<en>720x720dpi, high-gloss paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>720HighGloss</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>b7</ev_driverval>
<constraints>
<constraint sense="false">
<make>Canon</make>
<model>BJC-2100</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-600</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-250</model>
<arg_defval>na</arg_defval>
</constraint>
</constraints>
</enum_val>
<enum_val id="ev/721">
<ev_longname>
<en>720x720dpi, high resolution paper</en>
</ev_longname>
<!-- A multilingual <comments> block can appear here, too;
it should be treated as documentation for the user. -->
<ev_shortname>
<en>720HighRes</en>
<!-- Until someone tells me how to learn the user locale in
backends, the shortname must be monolingual in <en>! -->
</ev_shortname>
<ev_driverval>b8</ev_driverval>
<constraints>
<constraint sense="false">
<make>Canon</make>
<model>BJC-2100</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-600</model>
<arg_defval>na</arg_defval>
</constraint>
<constraint sense="false">
<make>Canon</make>
<model>BJC-250</model>
<arg_defval>na</arg_defval>
</constraint>
</constraints>
</enum_val>
</enum_vals>
</option>