diff options
Diffstat (limited to 'android_icu4j/src/main/java/android/icu/text/RuleBasedTransliterator.java')
| -rw-r--r-- | android_icu4j/src/main/java/android/icu/text/RuleBasedTransliterator.java | 112 |
1 files changed, 55 insertions, 57 deletions
diff --git a/android_icu4j/src/main/java/android/icu/text/RuleBasedTransliterator.java b/android_icu4j/src/main/java/android/icu/text/RuleBasedTransliterator.java index 65ba6d949..72aa1710b 100644 --- a/android_icu4j/src/main/java/android/icu/text/RuleBasedTransliterator.java +++ b/android_icu4j/src/main/java/android/icu/text/RuleBasedTransliterator.java @@ -1,7 +1,7 @@ /* GENERATED SOURCE. DO NOT MODIFY. */ /* ******************************************************************************* - * Copyright (C) 1996-2014, International Business Machines Corporation and * + * Copyright (C) 1996-2016, International Business Machines Corporation and * * others. All Rights Reserved. * ******************************************************************************* */ @@ -18,18 +18,18 @@ import java.util.Map; * To include a literal semicolon, prefix it with a backslash ('\'). * Unicode Pattern_White_Space is ignored. * If the first non-blank character on a line is '#', - * the entire line is ignored as a comment. </p> + * the entire line is ignored as a comment. * * <p>Each set of rules consists of two groups, one forward, and one * reverse. This is a convention that is not enforced; rules for one * direction may be omitted, with the result that translations in * that direction will not modify the source text. In addition, * bidirectional forward-reverse rules may be specified for - * symmetrical transformations.</p> + * symmetrical transformations. * - * <p><b>Rule syntax</b> </p> + * <p><b>Rule syntax</b> * - * <p>Rule statements take one of the following forms: </p> + * <p>Rule statements take one of the following forms: * * <dl> * <dt><code>$alefmadda=\u0622;</code></dt> @@ -83,7 +83,6 @@ import java.util.Map; * "<code>abc{def}</code>". Another example is "<code>{123}456</code>" * (or "<code>123}456</code>") in which the literal * pattern "<code>123</code>" must be followed by "<code>456</code>". - * </p> * * <p>The output string of a forward or reverse rule consists of * characters to replace the literal pattern characters. If the @@ -93,46 +92,46 @@ import java.util.Map; * next replacement, if any, will be applied. The cursor is usually * placed within the replacement text; however, it can actually be * placed into the precending or following context by using the - * special character '<code>@</code>'. Examples:</p> + * special character '<code>@</code>'. Examples: * * <blockquote> * <p><code>a {foo} z > | @ bar; # foo -> bar, move cursor * before a<br> * {foo} xyz > bar @@|; # foo -> bar, cursor between - * y and z</code></p> + * y and z</code> * </blockquote> * - * <p><b>UnicodeSet</b></p> + * <p><b>UnicodeSet</b> * * <p><code>UnicodeSet</code> patterns may appear anywhere that * makes sense. They may appear in variable definitions. * Contrariwise, <code>UnicodeSet</code> patterns may themselves * contain variable references, such as "<code>$a=[a-z];$not_a=[^$a]</code>", - * or "<code>$range=a-z;$ll=[$range]</code>".</p> + * or "<code>$range=a-z;$ll=[$range]</code>". * * <p><code>UnicodeSet</code> patterns may also be embedded directly - * into rule strings. Thus, the following two rules are equivalent:</p> + * into rule strings. Thus, the following two rules are equivalent: * * <blockquote> * <p><code>$vowel=[aeiou]; $vowel>'*'; # One way to do this<br> * [aeiou]>'*'; * # - * Another way</code></p> + * Another way</code> * </blockquote> * - * <p>See {@link UnicodeSet} for more documentation and examples.</p> + * <p>See {@link UnicodeSet} for more documentation and examples. * - * <p><b>Segments</b></p> + * <p><b>Segments</b> * * <p>Segments of the input string can be matched and copied to the * output string. This makes certain sets of rules simpler and more - * general, and makes reordering possible. For example:</p> + * general, and makes reordering possible. For example: * * <blockquote> * <p><code>([a-z]) > $1 $1; * # * double lowercase letters<br> - * ([:Lu:]) ([:Ll:]) > $2 $1; # reverse order of Lu-Ll pairs</code></p> + * ([:Lu:]) ([:Ll:]) > $2 $1; # reverse order of Lu-Ll pairs</code> * </blockquote> * * <p>The segment of the input string to be copied is delimited by @@ -140,12 +139,12 @@ import java.util.Map; * nine segments may be defined. Segments may not overlap. In the * output string, "<code>$1</code>" through "<code>$9</code>" * represent the input string segments, in left-to-right order of - * definition.</p> + * definition. * - * <p><b>Anchors</b></p> + * <p><b>Anchors</b> * * <p>Patterns can be anchored to the beginning or the end of the text. This is done with the - * special characters '<code>^</code>' and '<code>$</code>'. For example:</p> + * special characters '<code>^</code>' and '<code>$</code>'. For example: * * <blockquote> * <p><code>^ a > 'BEG_A'; # match 'a' at start of text<br> @@ -153,112 +152,111 @@ import java.util.Map; * of 'a'<br> * z $ > 'END_Z'; # match 'z' at end of text<br> * z > 'Z'; # match other instances - * of 'z'</code></p> + * of 'z'</code> * </blockquote> * * <p>It is also possible to match the beginning or the end of the text using a <code>UnicodeSet</code>. * This is done by including a virtual anchor character '<code>$</code>' at the end of the * set pattern. Although this is usually the match chafacter for the end anchor, the set will * match either the beginning or the end of the text, depending on its placement. For - * example:</p> + * example: * * <blockquote> * <p><code>$x = [a-z$]; # match 'a' through 'z' OR anchor<br> * $x 1 > 2; # match '1' after a-z or at the start<br> - * 3 $x > 4; # match '3' before a-z or at the end</code></p> + * 3 $x > 4; # match '3' before a-z or at the end</code> * </blockquote> * - * <p><b>Example</b> </p> + * <p><b>Example</b> * * <p>The following example rules illustrate many of the features of - * the rule language. </p> + * the rule language. * * <table border="0" cellpadding="4"> * <tr> - * <td valign="top">Rule 1.</td> - * <td valign="top" nowrap><code>abc{def}>x|y</code></td> + * <td style="vertical-align: top;">Rule 1.</td> + * <td style="vertical-align: top; write-space: nowrap;"><code>abc{def}>x|y</code></td> * </tr> * <tr> - * <td valign="top">Rule 2.</td> - * <td valign="top" nowrap><code>xyz>r</code></td> + * <td style="vertical-align: top;">Rule 2.</td> + * <td style="vertical-align: top; write-space: nowrap;"><code>xyz>r</code></td> * </tr> * <tr> - * <td valign="top">Rule 3.</td> - * <td valign="top" nowrap><code>yz>q</code></td> + * <td style="vertical-align: top;">Rule 3.</td> + * <td style="vertical-align: top; write-space: nowrap;"><code>yz>q</code></td> * </tr> * </table> * * <p>Applying these rules to the string "<code>adefabcdefz</code>" - * yields the following results: </p> + * yields the following results: * * <table border="0" cellpadding="4"> * <tr> - * <td valign="top" nowrap><code>|adefabcdefz</code></td> - * <td valign="top">Initial state, no rules match. Advance + * <td style="vertical-align: top; write-space: nowrap;"><code>|adefabcdefz</code></td> + * <td style="vertical-align: top;">Initial state, no rules match. Advance * cursor.</td> * </tr> * <tr> - * <td valign="top" nowrap><code>a|defabcdefz</code></td> - * <td valign="top">Still no match. Rule 1 does not match + * <td style="vertical-align: top; write-space: nowrap;"><code>a|defabcdefz</code></td> + * <td style="vertical-align: top;">Still no match. Rule 1 does not match * because the preceding context is not present.</td> * </tr> * <tr> - * <td valign="top" nowrap><code>ad|efabcdefz</code></td> - * <td valign="top">Still no match. Keep advancing until + * <td style="vertical-align: top; write-space: nowrap;"><code>ad|efabcdefz</code></td> + * <td style="vertical-align: top;">Still no match. Keep advancing until * there is a match...</td> * </tr> * <tr> - * <td valign="top" nowrap><code>ade|fabcdefz</code></td> - * <td valign="top">...</td> + * <td style="vertical-align: top; write-space: nowrap;"><code>ade|fabcdefz</code></td> + * <td style="vertical-align: top;">...</td> * </tr> * <tr> - * <td valign="top" nowrap><code>adef|abcdefz</code></td> - * <td valign="top">...</td> + * <td style="vertical-align: top; write-space: nowrap;"><code>adef|abcdefz</code></td> + * <td style="vertical-align: top;">...</td> * </tr> * <tr> - * <td valign="top" nowrap><code>adefa|bcdefz</code></td> - * <td valign="top">...</td> + * <td style="vertical-align: top; write-space: nowrap;"><code>adefa|bcdefz</code></td> + * <td style="vertical-align: top;">...</td> * </tr> * <tr> - * <td valign="top" nowrap><code>adefab|cdefz</code></td> - * <td valign="top">...</td> + * <td style="vertical-align: top; write-space: nowrap;"><code>adefab|cdefz</code></td> + * <td style="vertical-align: top;">...</td> * </tr> * <tr> - * <td valign="top" nowrap><code>adefabc|defz</code></td> - * <td valign="top">Rule 1 matches; replace "<code>def</code>" + * <td style="vertical-align: top; write-space: nowrap;"><code>adefabc|defz</code></td> + * <td style="vertical-align: top;">Rule 1 matches; replace "<code>def</code>" * with "<code>xy</code>" and back up the cursor * to before the '<code>y</code>'.</td> * </tr> * <tr> - * <td valign="top" nowrap><code>adefabcx|yz</code></td> - * <td valign="top">Although "<code>xyz</code>" is + * <td style="vertical-align: top; write-space: nowrap;"><code>adefabcx|yz</code></td> + * <td style="vertical-align: top;">Although "<code>xyz</code>" is * present, rule 2 does not match because the cursor is * before the '<code>y</code>', not before the '<code>x</code>'. * Rule 3 does match. Replace "<code>yz</code>" * with "<code>q</code>".</td> * </tr> * <tr> - * <td valign="top" nowrap><code>adefabcxq|</code></td> - * <td valign="top">The cursor is at the end; + * <td style="vertical-align: top; write-space: nowrap;"><code>adefabcxq|</code></td> + * <td style="vertical-align: top;">The cursor is at the end; * transliteration is complete.</td> * </tr> * </table> * * <p>The order of rules is significant. If multiple rules may match - * at some point, the first matching rule is applied. </p> + * at some point, the first matching rule is applied. * * <p>Forward and reverse rules may have an empty output string. * Otherwise, an empty left or right hand side of any statement is a - * syntax error. </p> + * syntax error. * * <p>Single quotes are used to quote any character other than a * digit or letter. To specify a single quote itself, inside or * outside of quotes, use two single quotes in a row. For example, * the rule "<code>'>'>o''clock</code>" changes the * string "<code>></code>" to the string "<code>o'clock</code>". - * </p> * - * <p><b>Notes</b> </p> + * <p><b>Notes</b> * * <p>While a RuleBasedTransliterator is being built, it checks that * the rules are added in proper order. For example, if the rule @@ -266,9 +264,9 @@ import java.util.Map; * then the second rule will throw an exception. The reason is that * the second rule can never be triggered, since the first rule * always matches anything it matches. In other words, the first - * rule <em>masks</em> the second rule. </p> + * rule <em>masks</em> the second rule. * - * <p>Copyright (c) IBM Corporation 1999-2000. All rights reserved.</p> + * <p>Copyright (c) IBM Corporation 1999-2000. All rights reserved. * * @author Alan Liu * @deprecated This API is ICU internal only. |