mime.types - mime type description file for cups
The mime.types file defines the recognized file types.
Additional file types can be added to mime.types or (preferably) in
additional files in the CUPS configuration directory with the extension
Each line in the mime.types file is a comment, blank, or rule line.
Comment lines start with the # character. Rule lines start with the
MIME type name and are optionally followed by a series of file
recognition rules that are used to automatically identify print and web
super/type rule [ ... ruleN]
MIME type names are case-insensitive and are sorted in ascending
alphanumeric order for the purposes of matching. See the "TYPE MATCHING
AND PRIORITY" section for more information.
The rules may be grouped using parenthesis, joined using "+" for a
logical AND and "," or whitespace for a logical OR, and negated using
Rules take two forms - a filename extension by itself and functions
with test values inside parenthesis. The following functions are
Pattern match on filename
True if bytes are valid printable ASCII (CR, NL, TAB, BS, 32-126)
True if bytes are printable 8-bit chars (CR, NL, TAB, BS, 32-126,
Specifies the relative priority of this MIME type. The default
priority is 100. Larger values have higher priority while smaller
values have lower priority.
True if bytes are identical to string
True if a case-insensitive comparison of the bytes is identical
True if byte is identical
True if 16-bit integer is identical
True if 32-bit integer is identical
True if current locale matches string
True if the range contains the string
String constants can be specified inside quotes ("") for strings
containing whitespace and angle brackets (<>) for hexadecimal strings.
TYPE MATCHING AND PRIORITY
When CUPS needs to determine the MIME type of a given file, it checks
every MIME type defined in the .types files. When two types have the
same matching rules, the type chosen will depend on the type name and
priority, with higher- priority types being used over lower-priority
ones. If the types have the same priority, the type names are sorted
alphanumerically in ascending order and the first type is chosen.
For example, if two types "text/bar" and "text/foo" are defined as
matching the extension "doc", normally the type "text/bar" will be
chosen since its name is alphanumerically smaller than "text/foo".
However, if "text/foo" also defines a higher priority than "text/bar",
"text/foo" will be chosen instead.
classes.conf(5), cupsd(8), cupsd.conf(5), mime.convs(5),
Copyright 2007-2009 by Apple Inc.