Bug: 4343280

Test:  I11f8518d9ee

Change-Id: I4b90bdffffed9736af223ac83c1a54019add70bb

Change-Id: I2c8b093b59ad36ffe860c3c4d360d87251d101c4

Bug: 4343280

Change-Id: I0f6a7e6912ed4abea07c10d266da4c7ccb0dae76

This finally makes active the behavior described in
Bug: 5968922

Change-Id: I363ed23270c3dea75411ea806011225097b5d07c

This stores the separator that was used to commit the word in
the LastComposedWord. It may be NOT_A_SEPARATOR if there was
no separator (for example, the cursor moved causing a commit,
or there was a manual pick). This is necessary to implement
feature request #5968922.

Change-Id: I5fcf19a78ec66d68d4df89418eaef13952588207

There is no point storing the prospective autocorrect - we are
recomputing it anyway. The committed word however will be necessary
to implement feature request #5968922.

Change-Id: I588c18e1a5a1050a791d601de465f421ccbe36cd

Change-Id: I61ff218ae2ca4eb443a370e581b677755258670a

Bug: 5961179
Change-Id: I452efc552c6ab390931f25557d7aee5a64bf054e

And unit test

Change-Id: Ic4fc3626f8b86e10156d770d41cd6deab5d31f39

Seems I didn't get how to iterate on a String correctly >.>
Talk about a big bug. Anyway, I think it's working now.

Bug: 5955228
Change-Id: I988c900cf2a16c44b9505cfd4f77c7cda7e592f0

Change-Id: Ifbe0d7e4eafea1926bbce968eae4724dd5769689

It turns out this can be removed entirely.

Change-Id: I6f23703cef1666311989a825285317eef696487f

Deactivate the LastComposedWord when the commit was not the right
type, instead of fooling it by passing it a null auto-correction.

Change-Id: I032b477dc691bd151a644ca4b0c9f0a9b5512e45

Remove the now useless WordComposer.CharacterStore class
and merge back its members inside WordComposer. This should
simplify the word composer a bit.

Change-Id: I5fe32418c62a583cd558dce98758a4701559bdf5

This is cleanup.
This also introduces a "deactivated" state to the last committed
word, that can be used for
Bug: 5875776

Change-Id: I1855adb8ac8123f6d2c5365b0ae899145e5c3ba1

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