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