4924N/A# This properties file is used to initialize the default
5751N/A# default mappings between common Mac OS X selection atoms and platform-independent
4924N/A# MIME type strings, which will be converted into
4924N/A# These default mappings may be augmented by specifying the
4924N/A# will be loaded into the SystemFlavorMap.
4924N/A# <native> should be a string identifier that the native platform will
4924N/A# recognize as a valid data format. <MIME type> should specify both a MIME
4924N/A# primary type and a MIME subtype separated by a '/'. The MIME type may include
4924N/A# parameters, where each parameter is a
key/value pair separated by '=', and
4924N/A# where each parameter to the MIME type is separated by a ';'.
4924N/A# Because SystemFlavorMap implements FlavorTable, developers are free to
4924N/A# duplicate both native keys and DataFlavor values. If a mapping contains a
4924N/A# duplicate key or value, earlier mappings which included this key or value
4924N/A# Mappings whose values specify DataFlavors with primary MIME types of
4924N/A# "text", and which support the charset parameter, should specify the exact
4924N/A# format in which the native platform expects the data. The "charset"
4924N/A# parameter specifies the char to byte encoding, the "eoln" parameter
4924N/A# specifies the end-of-line marker, and the "terminators" parameter specifies
4924N/A# the number of terminating NUL bytes. Note that "eoln" and "terminators"
4924N/A# are not standardized MIME type parameters. They are specific to this file
4924N/A# format ONLY. They will not appear in any of the DataFlavors returned by the
4924N/A# SystemFlavorMap at the Java level.
4924N/A# If the "charset" parameter is omitted, or has zero length, the platform
4924N/A# default encoding is assumed. If the "eoln" parameter is omitted, or has
4924N/A# zero length, "\n" is assumed. If the "terminators" parameter is omitted,
4924N/A# or has a value less than zero, zero is assumed.
4924N/A# Upon initialization, the data transfer subsystem will record the specified
4924N/A# details of the native text format, but the default SystemFlavorMap will
4924N/A# present a large set of synthesized DataFlavors which map, in both
4924N/A# directions, to the native. After receiving data from the application in one
4924N/A# of the synthetic DataFlavors, the data transfer subsystem will transform
4924N/A# the data stream into the format specified in this file before passing the
4924N/A# transformed stream to the native system.
4924N/A# Mappings whose values specify DataFlavors with primary MIME types of
4924N/A# "text", but which do not support the charset parameter, will be treated as
4924N/A# opaque, 8-bit data. They will not undergo any transformation process, and
4924N/A# any "charset", "eoln", or "terminators" parameters specified in this file
4924N/A# text flavors which support the charset parameter.
4924N/A# The COMPOUND_TEXT support for inter-client text transfer is disabled by
4924N/A# default. The reason is that many native applications prefer this format over
4924N/A# other native text formats, but are unable to decode the textual data in this
4924N/A# format properly. This results in java-to-native text transfer failures.
4924N/A# To enable the COMPOUND_TEXT support for this JRE installation uncomment