@@ -108,20 +108,23 @@ parent.link=../browser.html?tag=article
108108 the current locale and so forth.
109109 </dd>
110110 <dt>
111- {@link android.service.textservice.SpellCheckerService.Session#onGetSuggestions (TextInfo, int)
112- onGetSuggestions ()}
111+ {@link android.service.textservice.SpellCheckerService.Session#onGetSentenceSuggestionsMultiple (TextInfo[] , int)
112+ onGetSentenceSuggestionsMultiple ()}
113113 </dt>
114114 <dd>
115- Does the actual spell checking. This method returns an object containing
116- suggestions for the text passed to it.
115+ Does the actual spell checking. This method returns an array of
116+ {@link android.view.textservice.SentenceSuggestionsInfo} containing
117+ suggestions for the sentences passed to it.
117118 </dd>
118119 </dl>
119120 <p>
120121 Optionally, you can implement
121122 {@link android.service.textservice.SpellCheckerService.Session#onCancel()}, which
122- handles requests to cancel spell checking, or
123- {@link android.service.textservice.SpellCheckerService.Session#onGetSuggestionsMultiple(TextInfo[], int, boolean)
124- onGetSuggestionsMultiple()}, which handles batches of suggestion requests, or both.
123+ handles requests to cancel spell checking,
124+ {@link android.service.textservice.SpellCheckerService.Session#onGetSuggestions(TextInfo, int)
125+ onGetSuggestions()}, which handles a word suggestion request, or
126+ {@link android.service.textservice.SpellCheckerService.Session#onGetSuggestionsMultiple(TextInfo[], int, boolean)
127+ onGetSuggestionsMultiple()}, which handles batches of word suggestion requests.
125128 </p>
126129 <p>
127130 See the
@@ -208,7 +211,7 @@ onGetSuggestionsMultiple()}, which handles batches of suggestion requests, or bo
208211<h2 id="SpellCheckClient">Accessing the Spell Checker Service from a Client</h2>
209212<p>
210213 Applications that use {@link android.widget.TextView} views automatically benefit from spell
211- checking, because {@link android.widget.TextView} automatically uses a spelling checker. The
214+ checking, because {@link android.widget.TextView} automatically uses a spelling checker. The
212215 following screenshots show this:
213216</p>
214217<img src="{@docRoot}resources/articles/images/textview_spellcheck_screenshot_1.png" alt=""
@@ -224,7 +227,7 @@ onGetSuggestionsMultiple()}, which handles batches of suggestion requests, or bo
224227 The following diagram shows the flow of control for interacting with a spelling checker service:
225228</p>
226229<img src="{@docRoot}resources/articles/images/spellcheck_client_flow.png" alt=""
227- height="394 " id="figure3" />
230+ height="393 " id="figure3" />
228231<p class="img-caption">
229232 <strong>Figure 3.</strong> Interacting with a spelling checker service.
230233</p>
@@ -233,4 +236,4 @@ onGetSuggestionsMultiple()}, which handles batches of suggestion requests, or bo
233236 Spell Checker Client</a> sample app shows how to interact with a spelling checker service. The
234237 LatinIME input method editor in the Android Open Source Project also contains an example of
235238 spell checking.
236- </p>
239+ </p>
0 commit comments