Change-Id: I6009b3c1950ba32b7f1e205a3db2307fe0cd688e

bug: 6669677

Change-Id: I08193c26f76dbd48168f8ac02c1b737525bfc7b2

Bug: 7032858
Change-Id: I9f4d939fa87fdead4c5a5921338a16cd0a59b7ac

Change-Id: I7f2fe1771eed6b610704892b24f8a0283a779162

Change-Id: I6b4de9187e122298e5e9cd8ddc9070d062df6a89

Change-Id: Iff20dcb9ca0d6064bb118247887fe24b812c0c61

Change-Id: I5435cef8ac6be523934ffa394952cb120c8e89d6

Change-Id: I29d6afbcba0998558c9b19287a460d9f0e410994

The user history dictionary should be the one knowing it does not suggest words
beyond 2 characters, not Suggest.

Change-Id: Ie85ec6116eb495e0c7f51108e4620c5ae536f4bf

Change-Id: I5c27a3ed99b17f850e26a8503de16f001c7111c1

Change-Id: Ifd0d5b6978f76b841574a6e10157c32d0cd656b6

Stop storing an int in each of the different class types, and
just store a string in the top class.

Change-Id: I2af1832743e6fe78e5c1364f6d9cc21252bf5831

Bug: 6637614
Change-Id: I34d26563e59d3b09bf35b8173dac5645ccb6a39f

Bug: 6637614
Change-Id: I34d26563e59d3b09bf35b8173dac5645ccb6a39f

Change-Id: I03236386aea13fbd4fb8eaeee18e0008aa136502

Bug: 6584882
Change-Id: I1f76388fa8cc16171bc3fc60c935ddcf0a7c4e92

Bug: 6626700
Change-Id: I3190d7404e45e704be79ee2031e79b18475feb8c

Bug: 6603257
Change-Id: I73b65e921cff8337a00594525f67f6aec2178881

Bug: 6603257
Change-Id: I2e8017f9e2e222aeab0a80faa239ce83d3b212ad

Bug: 4192129
Change-Id: I867e78ce79c78977d08e8b66881a25b6fe5bf41f

Bug: 4192129

Change-Id: Idcc62e4f9696b56b1d7013891b2da37b1784423e

Bug: 4192129

Change-Id: Ic98398e5383093a1c24373849eadc48fc4d3626f

Bug: 6465474
Change-Id: Ifbfe0ddc2ce5fab070939ede3db7bf03a8535a45

Bug: 4646172

Change-Id: I51002c73d5bad1a698110c5cda02253348be8eed

Change-Id: Ied70a86bedb08adcf8353b189367172459f55292

Bug: 6236912
Change-Id: Ie09e5ef1c23eb48621ac3f2f2dc28dc2e46ca288

The old code would remove caps from the first letter if
auto-capsed but that makes very little sense when the word
is camel-cased. Also, it would not correctly handle
surrogate pairs, and would require a direct reference to
LatinIME and a specific method to do the processing in an
unexpected place.

Change-Id: I416d6a805242788a2473f007ca7452c9fe3f5205

UserBigramDictionary -> UserHistoryDictionary.

Also update all methods, strings and comments, except those needed
for backward compatibility (which only include the name of the
database file).

Change-Id: I0bccea29880dc566b90100575b83baaa947b03ae

bug: 6181736

Change-Id: I6522f19555c27f33c9ff4eaa8b2559a51a38f015

UserBigramDictionary now assumes both functionalities. It will
be renamed to UserHistoryDictionary in a future change.

There are several reasons to do this. First, there is a lot of
duplicate code in User{Unigram,Bigram}Dictionaries that are
factored by the few lines of code in this change. Also, other
dictionaries like BinaryDictionary or ContactsDictionary all
assume both responsibilities, as should be the case
theoretically.

It is also possible to do this because previous versions don't
write any unigram data that we'd want to reuse. For even older
versions that do write data, we can't really make any sense out
of it. Bigram data however can be useful, and this allows us to
reuse it easily.

Change-Id: I755525f92744e1536eaef097527e8151b7859a30

A lot of things don't really make sense in the old code.
Let's streamline it for now so that we have a cleaner interface
to work with. This is preliminary work for bug 4192129.

Change-Id: If01a5974cfadc43afced610c57fcf7fde67c1346

Bug: 6035465
Change-Id: Ibe2d542349ec598824f78b91d374a977082fc2d1

- 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

Change-Id: Ia23765268be0ef89d7fe7c3f5372ed32d6615765

This change also gets rid of several compiler warnings.

Change-Id: I23962edaadad18a6e0395d528af17b909dcf5dad

Bug: 4464446
Change-Id: If7b6d73fb408d53f941c82ed4f47221e85c845d8

This change also fixes copyright comments.

Bug: 4442045
Change-Id: I297a2c64e709fb0d613404e5f1de45d810f9de15

Change-Id: Iaceedc783181e43af6dd48ece218a42eace66532

This also fixes a small inconsistency upon clicking on whitespace
twice in a row.
Also add some unit tests for an introduced and an existing method.

Change-Id: I1be2fb53c9624f4d0f5299009632cb4384fdfc15

- Have user-history based bigrams used as soon as they are entered,
  not after 6 times.
- Limit bigram frequency to 255 (this limits the multiplier to 1.8, and
  has no effect on main dict bigrams which already have this limit)
- Some TODO resolving

bug: 4192129

Change-Id: I4777f1a58c43dd55381c4b01252d722ab3a70547