Change-Id: I04f1014ab3b115bd457e25a267d2e46d306c8a0e

Bug: 5023981
Change-Id: I737bacb1a6bb40f70be65d6eff85614afe6c79ed

This reverts commit be34d973.

Bug: 5023981
Change-Id: I34f75cde035f04a9a82c9259442ed0e255cb7118

This change also partialy reverts I5832421c, because of incorrect
popup mini key width calculation.

Bug: 5023981
Change-Id: I1acde090c01d3d861fcc5559cad81e638de2c2bb

This is a followup of Iea7f8f34.

Bug: 5023981
Change-Id: I1135383ff0f0a2b8a5940d0d5c407fd01706a7f7

This is a followup of Iea7f8f34.

Bug: 5023981
Change-Id: Ice6d949581aea7ca68799be2b91ff28234dd88d6

Bug: 5023981
Change-Id: Iea7f8f340775cbb093c50d6e741b2f1476e9ac39

Change-Id: I5832421cab3d496d4bb8a5e9902d0b5f4929fd0b

Change-Id: If13df42efffc7cef746c09d5abfe7a8619452a0b

Bug: 5227682
Change-Id: Iff93b425f52981b5e2c65e309b07bcfe4485eeb1

This fixes a race condition that would end up with the spell
checker not finding some words in the user dictionary when it
just booted.

Bug: 5194627
Change-Id: I1ba911cc53e6ae3b111d54a6f91d1d5feef3f5de

Bug: 5023981
Change-Id: Ib4fd55d52718aa244178ca2313f5e8487378324f

Change-Id: I7e9e6e5bc4486d8618d0213b112308c3d305c15e

Change-Id: I8cfad5f780a481a251cc4f752bff3cda5ae3ffbe

Bug: 5219037

Change-Id: I0300fbc7e1cc97f0f8ba4d21e0e699d9fe66ed76

Bug: 5218662
Change-Id: I094b2ceb7438148eb5bdf620b188f598e8442a07

Bug: 5218641
Change-Id: I88b3e7efa1f7c009c8a8e4f5453a5c4df2f91cfc

Bug: 5058488
Change-Id: Ib12013f58afad957a8205b439f87480cc12ea06f

...that was missing

Change-Id: Ia3b17909f295e0a93dee633c8d67c0e03840023e

The message this removes gets printed under normal conditions.
Normally dictionary files are compressed then crypted, but not
compressed a second time; however LatinIME tries to open a
compressed-crypted-compressed file first, because it could not
do it afterwards and we want to support this case. So under
normal operations, the first method LatinIME tries is actually
expected to fail.
Also, if we decide to stop compressing or/and encrypting dicts
LatinIME supports it as a valid use case. It should not print
errors to the log.

If the file cannot be open at all, then it is an unexpected
case, and Latin IME still reports to the log.

Change-Id: Ic5228c51365a101af1d03e2c893484d3050b5a1c

This change also tweaks more_suggestions_hint drawables to eliminate
unnecessarily padding at the bottom.

Bug: 5204563
Change-Id: If5ec731c9a490da0116a020e8fd405c7d025d707

Bug: 5095140
Change-Id: I7000f752bc9b7fd6a7af4839b2f225c085300128

This is preparation to have the decrypting/unzipping code
moved over to LatinIME.

Bug: 5095140
Change-Id: Ic3fdcc3de673b46cef2eb9ebe6a52cbdd614e50a

This change also introduces "AsciiCapable" extra value for subtype
that indicates the subtype can input any ASCII code point from its
keyboard layout.

Only if the input field has "forceAscii" private IME option and the
current subtype doesn't have "AsciiCapable" extra value, the en_US
keyboard layout will be used for the input field.

Bug: 3384942
Change-Id: I25e2553e37ecb5002df1164e45f6273845fe463b

Change-Id: I3ea8ffcdefcefaa82ae76a31bb65977009d8a040

Bug: 5182291
Change-Id: I5089a14902b9f4ff1ab4f34e3f7a42aca5040d3e

LatinIME has several fallbacks to ensure a dictionary is used.
However, it should now be possible to deactivate the main dictionary
through the dictionary pack settings. In this case, Latin IME should
not fallback to the built-in dictionary.

Change-Id: Ibd992ad89793169f04a968b40781fce819b87b6f

Change-Id: Ia92ec4612090b03829db9a87ce68d701db6e15bc

Bug: 5182291
Change-Id: I6a88ed4df3ec98e31ea4966d82da56f7fca342ac

Change-Id: Iaf1b4bbb54be7a4cade856d1ba363e976774f442

Bug: 4311428
Change-Id: Ie7e094ded9c7c1fe811b7eb97bc33ffecb29a73c

This also adds some optional debug code to detect more easily possible
future occurrences of the same problem.

Bug: 5195017
Change-Id: I2558b468e46f7090de868f1ec2dc9e24895d670f

Bug: 5182291
Change-Id: I699ecef6fb8ea492d96fca1939f51faf0aac7fa6

This change also shows the valid typed word in bold face.

Bug: 5161713
Change-Id: I15355a11888fc8ef90ecc8b64a52eb08c1a2b367

Bug: 5175740
Change-Id: I592401b3b8c3074d70e06dc3a9919cc3cb47ba49

Bug: 4311428
Change-Id: Ic93f264101d13963503fcd447a69bbffd06e69f3

The new behavior is as follows:
- If the word in the dictionary is not fully lower case, then the
exact case is required to match.
- If the word in the dictionary is fully lower case, then any of
the following patterns match:
  - fully lower case
  - only the first char capitalized
  - all caps
Any other capitalization is rejected.

This is probably what people want. If you type a name in all lower
case, it should be marked as a typo, but if you type a word with a
capital for emphasis or just because it's the start of the sentence,
it should match a lower case word in the dictionary. If you have
a spurious capital letter in the middle of a word because of a typo,
it should be marked as such.

Accents are not affected, and should not be. An accented letter
is a different letter and a missing accent should be reported.
We should maybe consider again for some common transpositions
like the "ue" digraph for German, which is now considered a typo,
but will suggest the correct diacritics as the first suggestion.

Bug: 5145751
Change-Id: I651e24f13c90fb94700a1674ad380e95336e7dca

by ignoring its preference value, when the "show settings key option" in
the settings is disabled.

Change-Id: I934be2d9eb0bf6bf731e03f5d9b752de4a7a1c7c

This is preparation for bug: 5175740

Change-Id: I18b2042317f740cb1e021d3dfbf90ecfbb1a1d37

Bug: 5175868
Change-Id: I165eee4c865caa5ee1daf3e0b1acde8788b996ef