Change-Id: Ia62ef33b5c777a258b02280bda1b8368780a7eef

Change-Id: Ie0ea02a061dd0cb84db5f33113ff433584636bc7

Change-Id: Idf47f2e2bdd1d6394fc4b1ab7df28d64a808da1e

Change-Id: I87498799e6a48b8fa65924a098bb0ceb7626dce1

Change-Id: I16fa4099c75faac35344b0e4d3c2b866ddac896a

Auto-correct cancellation would sometimes kick in at
wrong times, causing crashes.

Bug: 5784542
Change-Id: I68dd6b8d9237ce9b66af2dc63e77ba6dd5fd69dd

Change-Id: I31cce9db471dcd4a7b3477bcb037a8ff482b7696

Change-Id: I68c667b00dadf2ed9f1c62fb7da37d2cf499cd81

...instead of the hard-to-understand mHasUncommittedTypedChars.
This is possible because now the word composer is actually aware
of commits.

Change-Id: I36b664ce8402a280f801e87b9ebe161f416b0853

Change-Id: I04e691fbc9227d4df195429bca89edea93575347

Currently, these variables hold the info about the composing
word, or maybe some outdated info, and it's not very clear
which it is. LatinIME is maintaining the freshness info in
a separate boolean, and uses it throughout the code for many,
many things, leading to much confusion.
The idea in grouping this info is, it can be saved in another
instance and restored later. It can be tested against to know
whether there is actually outdated but kept info or not, and
it should allow to straighten out what is actually currently
being typed. Ultimately, it will eliminate the need for
LatinIME to keep track of the status of the info in the
word composer.

Change-Id: I00e2c690f303f8320c9be35590a6df4583e9e456

- Stop the word composer from escaping - take a page from the law
  of Demeter and only report what is actually needed.
- Fix typos in comments.
- Add a comment for a fishy processing.
- Remove a useless local variable.

Change-Id: I5fa78901cbb5483fc9683bfb7094f47244b85df6

mBestWord has a confusing name - it's actually an auto-correction.
It's cleaner if it lives in the word composer because an
auto-correction should be tied to a specific user input, and
should be reset each time the user input changes to avoid
race conditions.

Change-Id: I718d29395bc747372067e6440e090c6a181994ae

This is awesome cleanup.

Change-Id: I35ce8940a13f3084630dc26d6e7e397acfdaac36

Change-Id: I7596ce3ae52fde436d06c2dd95ae873c7aa5ef7f

Bug: 5515381
Change-Id: I26fea896feaf2e9716c7ae3d4f2630360f23ac50

Bug: 5665809
Change-Id: I4d9100dbe980861ccb55c78464524be670cac1f7

Single quote at start of word is not considered a part of a
word any more.
Single quote at the end of a word now behave like capitalization:
lookup in the dictionary is done *disregarding* a final quote,
and it is forcefully added back into the suggestions afterwards.

Bug: 5566368
Change-Id: I14dd3815f4b743edba56d64a3abdf4b73d863a6a

Change-Id: Ia23765268be0ef89d7fe7c3f5372ed32d6615765

This is a follow up change of If6c0edef.
This is a cherry-pick of Idb415f53 from Master.

Bug: 5328922
Change-Id: I36d8bda9fb95e4809598296226c598a9f08bd8bb

This is a follow up change of If6c0edef.

Bug: 5328922
Change-Id: Idb415f53f3fea6660c7802577d08b4d89d4e7842

There is no definite path known for this to end up being
touched by other classes, but we could imagine through
some way or some other it ends up shoved in the stringbuilder
pool, leading to catastrophic results.

Hopefully related to
Bug: 5248688

Change-Id: Ib8abfc31263cbf31d515ed607ced5d8253971938

Change-Id: If6c0edef2334f018f2e04c6034f8ce747206f150

Bug: 4409091

Change-Id: I6efd23ebb9528bf1bd35320057a0ea264c187451

Change-Id: I0641f333bbc7d4ac27361c97252c4591584efb9d

Bug: 3311719

Change-Id: Ie596304070e321ad23fb67a13bf05e2b6af1b54b

Bug: 3428942
Change-Id: Id62f467ce4e50c60a56d59bf96770e799a4659e2

bug:3014227
Change-Id: Ic453e2fde57ce51be00f3a506e1c9328103ca99a

Bug: 3028277
Change-Id: I1c4d8dca4db8a70f851589d1fbd45a16ea1bfc1b

- remove unused code
- add @Override
- change the inappropriate cast

Change-Id: Ib25b4939e5b4273794ab0f6349776b5b62d89894

TODO: Cleanup will follow.

Change-Id: I4a68ba9f2f55760aa24187f1f13fdfa8a0b70963

- Fixed caching of words - some StringBuilders were being recycled while also being cached. Making copies now.
- Fixed regression in revert - don't reset the word composer after saving the accepted word.
- Removed flicker when cursoring through a word - delay the abortCorrection() until we need to and do the correction
   as an atomic operation.
- Fixed replacing of "selected" words (double-tap to select a word)

Still to do:
- Remove flicker on highlighting a word - may need a framework change
- Don't remove spans on text that's already in the text field - may require a framework change.
- Figure out what to do about the punctuations that share the suggestion strip when in correction mode.

Change-Id: I475c2fa7604f91659100510079fa13c7615177e9

Added tests for the dictionary lookup and correction logic on the primary dictionary.
This exercises part of the Suggest class and the native dictionary lookup code.

-use AOSP copyright instead of Google
-add NOTICE and tag file

Bug: 2548782
Change-Id: If50b2e9e9cc4b4876b0d047fc9f34e2d537a6da4

Bug: 2513996

The array of adjacent letters did not have the primary code in the first
position. Swap the codes around to make the primary the first one.

Change-Id: Id753254c88d440d3d76dbc048d123dfc78edf58d

Move java code to a different directory so that the unbundled
version doesn't try to compile the native code again.

Change-Id: I05cf9e643824ddc448821f69805ccb0240c5b986

If a user creates a new word at the beginning of a sentence, then don't
add it as a capitalized word in the dictionary.

Makes the user/contacts dictionary lookup faster. This is necessary because
there's more in these dictionaries now and it's written in Java.

Fix an auto-caps issue when moving the cursor. And do it a little lazily.

Fixed a bug that was causing user dictionary words to get a much
higher weightage than the main dictionary.