3 # This properties file is used to initialize the default
4 # java.awt.datatransfer.SystemFlavorMap. It contains the X11 platform-specific,
5 # default mappings between common X11 selection atoms and platform-independent
6 # MIME type strings, which will be converted into
7 # java.awt.datatransfer.DataFlavors.
9 # These default mappings may be augmented by specifying the
11 # AWT.DnD.flavorMapFileURL
13 # property in the appropriate awt.properties file. The specified properties URL
14 # will be loaded into the SystemFlavorMap.
16 # The standard format is:
18 # <native>=<MIME type>
20 # <native> should be a string identifier that the native platform will
21 # recognize as a valid data format. <MIME type> should specify both a MIME
22 # primary type and a MIME subtype separated by a '/'. The MIME type may include
23 # parameters, where each parameter is a key/value pair separated by '=', and
24 # where each parameter to the MIME type is separated by a ';'.
26 # Because SystemFlavorMap implements FlavorTable, developers are free to
27 # duplicate both native keys and DataFlavor values. If a mapping contains a
28 # duplicate key or value, earlier mappings which included this key or value
31 # Mappings whose values specify DataFlavors with primary MIME types of
32 # "text", and which support the charset parameter, should specify the exact
33 # format in which the native platform expects the data. The "charset"
34 # parameter specifies the char to byte encoding, the "eoln" parameter
35 # specifies the end-of-line marker, and the "terminators" parameter specifies
36 # the number of terminating NUL bytes. Note that "eoln" and "terminators"
37 # are not standardized MIME type parameters. They are specific to this file
38 # format ONLY. They will not appear in any of the DataFlavors returned by the
39 # SystemFlavorMap at the Java level.
41 # If the "charset" parameter is omitted, or has zero length, the platform
42 # default encoding is assumed. If the "eoln" parameter is omitted, or has
43 # zero length, "\n" is assumed. If the "terminators" parameter is omitted,
44 # or has a value less than zero, zero is assumed.
46 # Upon initialization, the data transfer subsystem will record the specified
47 # details of the native text format, but the default SystemFlavorMap will
48 # present a large set of synthesized DataFlavors which map, in both
49 # directions, to the native. After receiving data from the application in one
50 # of the synthetic DataFlavors, the data transfer subsystem will transform
51 # the data stream into the format specified in this file before passing the
52 # transformed stream to the native system.
54 # Mappings whose values specify DataFlavors with primary MIME types of
55 # "text", but which do not support the charset parameter, will be treated as
56 # opaque, 8-bit data. They will not undergo any transformation process, and
57 # any "charset", "eoln", or "terminators" parameters specified in this file
60 # See java.awt.datatransfer.DataFlavor.selectBestTextFlavor for a list of
61 # text flavors which support the charset parameter.
63 UTF8_STRING=text/plain;charset=UTF-8;eoln="\n";terminators=0
65 # The COMPOUND_TEXT support for inter-client text transfer is disabled by
66 # default. The reason is that many native applications prefer this format over
67 # other native text formats, but are unable to decode the textual data in this
68 # format properly. This results in java-to-native text transfer failures.
69 # To enable the COMPOUND_TEXT support for this JRE installation uncomment
72 # COMPOUND_TEXT=text/plain;charset=x-compound-text;eoln="\n";terminators=0
74 TEXT=text/plain;eoln="\n";terminators=0
75 STRING=text/plain;charset=iso8859-1;eoln="\n";terminators=0
76 FILE_NAME=application/x-java-file-list;class=java.util.List
77 PNG=image/x-java-image;class=java.awt.Image
78 JFIF=image/x-java-image;class=java.awt.Image