summaryrefslogtreecommitdiff
path: root/android_icu4j/src/main/java/android/icu/text/SelectFormat.java
diff options
context:
space:
mode:
Diffstat (limited to 'android_icu4j/src/main/java/android/icu/text/SelectFormat.java')
-rw-r--r--android_icu4j/src/main/java/android/icu/text/SelectFormat.java55
1 files changed, 27 insertions, 28 deletions
diff --git a/android_icu4j/src/main/java/android/icu/text/SelectFormat.java b/android_icu4j/src/main/java/android/icu/text/SelectFormat.java
index 266ff5f01..cb95b3d2d 100644
--- a/android_icu4j/src/main/java/android/icu/text/SelectFormat.java
+++ b/android_icu4j/src/main/java/android/icu/text/SelectFormat.java
@@ -1,7 +1,7 @@
/* GENERATED SOURCE. DO NOT MODIFY. */
/*
*******************************************************************************
- * Copyright (C) 2004-2011, International Business Machines Corporation and *
+ * Copyright (C) 2004-2016, International Business Machines Corporation and *
* others. All Rights Reserved. *
* Copyright (C) 2009 , Yahoo! Inc. *
*******************************************************************************
@@ -22,19 +22,19 @@ import android.icu.impl.PatternProps;
* how to map keywords to phrases and provides a default phrase. The
* object provided to the format method is a string that's matched
* against the keywords. If there is a match, the corresponding phrase
- * is selected; otherwise, the default phrase is used.</p>
+ * is selected; otherwise, the default phrase is used.
*
- * <h4>Using <code>SelectFormat</code> for Gender Agreement</h4>
+ * <h3>Using <code>SelectFormat</code> for Gender Agreement</h3>
*
* <p>Note: Typically, select formatting is done via <code>MessageFormat</code>
* with a <code>select</code> argument type,
- * rather than using a stand-alone <code>SelectFormat</code>.</p>
+ * rather than using a stand-alone <code>SelectFormat</code>.
*
* <p>The main use case for the select format is gender based inflection.
* When names or nouns are inserted into sentences, their gender can affect pronouns,
* verb forms, articles, and adjectives. Special care needs to be
* taken for the case where the gender cannot be determined.
- * The impact varies between languages:</p>
+ * The impact varies between languages:
*
* <ul>
* <li>English has three genders, and unknown gender is handled as a special
@@ -43,16 +43,16 @@ import android.icu.impl.PatternProps;
* The gender only affects pronouns: "he", "she", "it", "they".
*
* <li>German differs from English in that the gender of nouns is rather
- * arbitrary, even for nouns referring to people ("M&#u00E4;dchen", girl, is neutral).
+ * arbitrary, even for nouns referring to people ("M&#xE4;dchen", girl, is neutral).
* The gender affects pronouns ("er", "sie", "es"), articles ("der", "die",
- * "das"), and adjective forms ("guter Mann", "gute Frau", "gutes M&#u00E4;dchen").
+ * "das"), and adjective forms ("guter Mann", "gute Frau", "gutes M&#xE4;dchen").
*
* <li>French has only two genders; as in German the gender of nouns
* is rather arbitrary - for sun and moon, the genders
* are the opposite of those in German. The gender affects
* pronouns ("il", "elle"), articles ("le", "la"),
* adjective forms ("bon", "bonne"), and sometimes
- * verb forms ("all&#u00E9;", "all&#u00E9e;").
+ * verb forms ("all&#xE9;", "all&#xE9;e").
*
* <li>Polish distinguishes five genders (or noun classes),
* human masculine, animate non-human masculine, inanimate masculine,
@@ -61,16 +61,16 @@ import android.icu.impl.PatternProps;
*
* <p>Some other languages have noun classes that are not related to gender,
* but similar in grammatical use.
- * Some African languages have around 20 noun classes.</p>
+ * Some African languages have around 20 noun classes.
*
* <p><b>Note:</b>For the gender of a <i>person</i> in a given sentence,
- * we usually need to distinguish only between female, male and other/unknown.</p>
+ * we usually need to distinguish only between female, male and other/unknown.
*
* <p>To enable localizers to create sentence patterns that take their
* language's gender dependencies into consideration, software has to provide
* information about the gender associated with a noun or name to
* <code>MessageFormat</code>.
- * Two main cases can be distinguished:</p>
+ * Two main cases can be distinguished:
*
* <ul>
* <li>For people, natural gender information should be maintained for each person.
@@ -89,40 +89,40 @@ import android.icu.impl.PatternProps;
* would be provided: The name of the person as argument 0, the gender of
* the person as argument 1, and the name of the city as argument 2.
* The sentence pattern for English, where the gender of the person has
- * no impact on this simple sentence, would not refer to argument 1 at all:</p>
+ * no impact on this simple sentence, would not refer to argument 1 at all:
*
* <pre>{0} went to {2}.</pre>
*
* <p><b>Note:</b> The entire sentence should be included (and partially repeated)
* inside each phrase. Otherwise translators would have to be trained on how to
* move bits of the sentence in and out of the select argument of a message.
- * (The examples below do not follow this recommendation!)</p>
+ * (The examples below do not follow this recommendation!)
*
* <p>The sentence pattern for French, where the gender of the person affects
- * the form of the participle, uses a select format based on argument 1:</p>
+ * the form of the participle, uses a select format based on argument 1:
*
- * <pre>{0} est {1, select, female {all&#u00E9;e} other {all&#u00E9;}} &#u00E0; {2}.</pre>
+ * <pre>{0} est {1, select, female {all&#xE9;e} other {all&#xE9;}} &#xE0; {2}.</pre>
*
* <p>Patterns can be nested, so that it's possible to handle interactions of
* number and gender where necessary. For example, if the above sentence should
* allow for the names of several people to be inserted, the following sentence
* pattern can be used (with argument 0 the list of people's names,
* argument 1 the number of people, argument 2 their combined gender, and
- * argument 3 the city name):</p>
+ * argument 3 the city name):
*
* <pre>{0} {1, plural,
- * one {est {2, select, female {all&#u00E9;e} other {all&#u00E9;}}}
- * other {sont {2, select, female {all&#u00E9;es} other {all&#u00E9;s}}}
- * }&#u00E0; {3}.</pre>
+ * one {est {2, select, female {all&#xE9;e} other {all&#xE9;}}}
+ * other {sont {2, select, female {all&#xE9;es} other {all&#xE9;s}}}
+ * }&#xE0; {3}.</pre>
*
* <h4>Patterns and Their Interpretation</h4>
*
* <p>The <code>SelectFormat</code> pattern string defines the phrase output
* for each user-defined keyword.
* The pattern is a sequence of (keyword, message) pairs.
- * A keyword is a "pattern identifier": [^[[:Pattern_Syntax:][:Pattern_White_Space:]]]+</p>
+ * A keyword is a "pattern identifier": [^[[:Pattern_Syntax:][:Pattern_White_Space:]]]+
*
- * <p>Each message is a MessageFormat pattern string enclosed in {curly braces}.</p>
+ * <p>Each message is a MessageFormat pattern string enclosed in {curly braces}.
*
* <p>You always have to define a phrase for the default keyword
* <code>other</code>; this phrase is returned when the keyword
@@ -130,21 +130,20 @@ import android.icu.impl.PatternProps;
* the <code>format</code> method matches no other keyword.
* If a pattern does not provide a phrase for <code>other</code>, the method
* it's provided to returns the error <code>U_DEFAULT_KEYWORD_MISSING</code>.
- * <br/>
+ * <br>
* Pattern_White_Space between keywords and messages is ignored.
- * Pattern_White_Space within a message is preserved and output.</p>
+ * Pattern_White_Space within a message is preserved and output.
*
- * <p><pre>Example:
+ * <pre>Example:
* MessageFormat msgFmt = new MessageFormat("{0} est " +
- * "{1, select, female {all&#u00E9;e} other {all&#u00E9;}} &#u00E0; Paris.",
+ * "{1, select, female {all&#xE9;e} other {all&#xE9;}} &#xE0; Paris.",
* new ULocale("fr"));
* Object args[] = {"Kirti","female"};
* System.out.println(msgFmt.format(args));
* </pre>
* <p>
- * Produces the output:<br/>
- * <code>Kirti est all&#u00E9;e &#u00E0; Paris.</code>
- * </p>
+ * Produces the output:<br>
+ * <code>Kirti est all&#xE9;e &#xE0; Paris.</code>
*/
public class SelectFormat extends Format{