java.lang.Objectjava.text.Collator
All Implemented Interfaces:
Comparator, Cloneable
Direct Known Subclasses:
RuleBasedCollator
Collator class performs locale-sensitive
String comparison. You use this class to build
searching and sorting routines for natural language text.
Collator is an abstract base class. Subclasses
implement specific collation strategies. One subclass,
RuleBasedCollator, is currently provided with
the Java Platform and is applicable to a wide set of languages. Other
subclasses may be created to handle more specialized needs.
Like other locale-sensitive classes, you can use the static
factory method, getInstance, to obtain the appropriate
Collator object for a given locale. You will only need
to look at the subclasses of Collator if you need
to understand the details of a particular collation strategy or
if you need to modify that strategy.
The following example shows how to compare two strings using
the Collator for the default locale.
// Compare two strings in the default locale
Collator myCollator = Collator.getInstance();
if( myCollator.compare("abc", "ABC") < 0 )
System.out.println("abc is less than ABC");
else
System.out.println("abc is greater than or equal to ABC");
You can set a Collator's strength property
to determine the level of difference considered significant in
comparisons. Four strengths are provided: PRIMARY,
SECONDARY, TERTIARY, and IDENTICAL.
The exact assignment of strengths to language features is
locale dependant. For example, in Czech, "e" and "f" are considered
primary differences, while "e" and "ě" are secondary differences,
"e" and "E" are tertiary differences and "e" and "e" are identical.
The following shows how both case and accents could be ignored for
US English.
//Get the Collator for US English and set its strength to PRIMARY
Collator usCollator = Collator.getInstance(Locale.US);
usCollator.setStrength(Collator.PRIMARY);
if( usCollator.compare("abc", "ABC") == 0 ) {
System.out.println("Strings are equivalent");
}
For comparing Strings exactly once, the compare
method provides the best performance. When sorting a list of
Strings however, it is generally necessary to compare each
String multiple times. In this case, CollationKeys
provide better performance. The CollationKey class converts
a String to a series of bits that can be compared bitwise
against other CollationKeys. A CollationKey is
created by a Collator object for a given String.
Note: CollationKeys from different
Collators can not be compared. See the class description
for CollationKey
for an example using CollationKeys.
Helena - Shih, Laura Werner, Richard Gillam| Field Summary | ||
|---|---|---|
| public static final int | PRIMARY | Collator strength value. When set, only PRIMARY differences are
considered significant during comparison. The assignment of strengths
to language features is locale dependant. A common example is for
different base letters ("a" vs "b") to be considered a PRIMARY difference.
|
| public static final int | SECONDARY | Collator strength value. When set, only SECONDARY and above differences are
considered significant during comparison. The assignment of strengths
to language features is locale dependant. A common example is for
different accented forms of the same base letter ("a" vs "\u00E4") to be
considered a SECONDARY difference.
|
| public static final int | TERTIARY | Collator strength value. When set, only TERTIARY and above differences are
considered significant during comparison. The assignment of strengths
to language features is locale dependant. A common example is for
case differences ("a" vs "A") to be considered a TERTIARY difference.
|
| public static final int | IDENTICAL | Collator strength value. When set, all differences are considered significant during comparison. The assignment of strengths to language features is locale dependant. A common example is for control characters ("\u0001" vs "\u0002") to be considered equal at the PRIMARY, SECONDARY, and TERTIARY levels but different at the IDENTICAL level. Additionally, differences between pre-composed accents such as "\u00C0" (A-grave) and combining accents such as "A\u0300" (A, combining-grave) will be considered significant at the IDENTICAL level if decomposition is set to NO_DECOMPOSITION. |
| public static final int | NO_DECOMPOSITION | Decomposition mode value. With NO_DECOMPOSITION
set, accented characters will not be decomposed for collation. This
is the default setting and provides the fastest collation but
will only produce correct results for languages that do not use accents.
|
| public static final int | CANONICAL_DECOMPOSITION | Decomposition mode value. With CANONICAL_DECOMPOSITION
set, characters that are canonical variants according to Unicode
standard will be decomposed for collation. This should be used to get
correct collation of accented characters.
CANONICAL_DECOMPOSITION corresponds to Normalization Form D as described in Unicode Technical Report #15.
|
| public static final int | FULL_DECOMPOSITION | Decomposition mode value. With FULL_DECOMPOSITION
set, both Unicode canonical variants and Unicode compatibility variants
will be decomposed for collation. This causes not only accented
characters to be collated, but also characters that have special formats
to be collated with their norminal form. For example, the half-width and
full-width ASCII and Katakana characters are then collated together.
FULL_DECOMPOSITION is the most complete and therefore the slowest
decomposition mode.
FULL_DECOMPOSITION corresponds to Normalization Form KD as described in Unicode Technical Report #15.
|
| static final int | LESS | LESS is returned if source string is compared to be less than target
string in the compare() method.
|
| static final int | EQUAL | EQUAL is returned if source string is compared to be equal to target
string in the compare() method.
|
| static final int | GREATER | GREATER is returned if source string is compared to be greater than
target string in the compare() method.
|
| Constructor: |
|---|
|
| Method from java.text.Collator Summary: |
|---|
| clone, compare, compare, equals, equals, getAvailableLocales, getCollationKey, getDecomposition, getInstance, getInstance, getStrength, hashCode, setDecomposition, setStrength |
| Methods from java.lang.Object: |
|---|
| clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method from java.text.Collator Detail: |
|---|
|
For a one time comparison, this method has the best performance. If a given String will be involved in multiple comparisons, CollationKey.compareTo has the best performance. See the Collator class description for an example using CollationKeys. |
This implementation merely returns
|
|
|
getInstance methods of this class can return
localized instances.
The returned array represents the union of locales supported
by the Java runtime and by installed
CollatorProvider implementations.
It must contain at least a Locale instance equal to
Locale.US . |
|
The three values for decomposition mode are: |
|
|
|
|
|
|