Gecko [ www.utparral.edu.mx ]

Name	Size	Permission
__pycache__	[ DIR ]	drwxrwxr-x
preferreddrivers.rng	7.31 KB	-rw-r--r--
validate.py	2.49 KB	-rw-r--r--

Code Editor : preferreddrivers.rng

<?xml version="1.0" encoding="UTF-8"?>

<!--
   This type of file is for ordering named PPD files for a given
   printer.

When choosing a driver for a known printer, first the complete list
   of available drivers is compiled.  This includes any generic
   drivers that are likely to be able to drive the device, based on
   its IEEE 1284 Device ID's COMMAND SET field.

The next task is to present this list to the user in order of
   preference, i.e. the drivers most likely to be the "right" ones
   first.

This is done with reference to an XML file of the type described
   here.

Child elements of the preferenceorder element are processed in
   order, with each printer element being matched against the printer
   in question.  Once all the elements have been processed, the result
   will be a list of driver types in preference order (most preferred
   first), and a set of blacklisted driver types.

For each printer element, at least one of the make-and-model and
   deviceid elements must match.  A deviceid element matches if all of
   the field regular expressions match.  For a matching printer
   element, the driver types matching each pattern contained in the
   drivers, avoid, and blacklist elements are appended to separate
   lists for drivers to use, drivers to avoid, and drivers that must
   not be used.

A printer element that does not contain any make-and-model or
   deviceid elements is a "catch-all" element and matches any
   printer.

To convert this into a list of drivers (i.e. PPDs), the drivertypes
   element is examined.  Each PPD is assigned a driver type name, and
   then the PPDs are arranged in order corresponding to the list of
   preferred driver types.  Drivers in the avoid list are then placed
   at the end of the list, and drivers in the blacklist are removed
   altogether.

To determine the driver type name for a PPD, the child elements of
   the drivertypes element are examined.  For each drivertype element,
   the criteria elements defined are matched against the PPD
   attributes.  If all criteria are satisfied, this PPD's driver type
   is given by the "name" attribute of the containing drivertype
   element.  In this case, no further drivertype elements are
   examined.

If there are no criteria defined by a driver type, it is considered
   to match (i.e. it is a "catch-all" type).
  -->

<define name="drivertypes">
    <element name="drivertypes">
      <zeroOrMore>
	
	<ref name="drivertype"/>
      </zeroOrMore>
    </element>
  </define>

<interleave>
	<optional>
	  <ref name="ppdname"/>
	</optional>

<value>exact-cmd</value>

<value>exact</value>

<value>close</value>

<value>generic</value>

<value>none</value>
	  </choice>
	</oneOrMore>
      </list>
    </element>
  </define>

<define name="preferenceorder">
    <element name="preferenceorder">
      <zeroOrMore>
	
	<ref name="printer"/>
      </zeroOrMore>
    </element>
  </define>

<optional>
	<element name="make-and-model">
	  <attribute name="match">
	    
	    <data type="string"/>
	  </attribute>
	  <empty/>
	</element>
      </optional>

${this.title}

Code Editor : preferreddrivers.rng