* commit 'f224941c':
  Suppress calling onPressKey and onReleaseKey while detecting gesture

* commit 'bfb07ed7':
  Add preference dependency to gesture input related options

Bug: 8613600
Change-Id: I279d3264080aede59203205c45763c7f8ff08ae6

* commit '1903b41f':
  Clean up tests and increase speed

Conservatively reduce the number of unigrams to test from 1000
to 100.

Bug: 8583091
Change-Id: I48621ec44ff5f0590640d7c6b174ab5a6d267aaf

* commit 'e2af9b7e':
  Reset vertical correction when more suggestions are in modal mode

Bug: 8605150
Change-Id: Iadbebfb80e765c97e58e8524eb87419f2a9e41d4

* commit 'c2653d0b':
  Fix a typo

Change-Id: I27b925be030e9e6ee8ae49dc13f39accec996d7e

* commit '03d1dff3':
  Fix Binary dict tests

There are two problems here. The first one is the tests would send
an invalid unicode character. Although we could want dicttool to
handle this more gracefully, it's fine for now.

The second problem is much more serious. If a node has more than
128 children, then the java code will crash trying to read the
dictionary back because of a bug that this change fixes. In
theory, it's possible that happens when we try to load the user
history dictionary back from the disk - native code is not affected
so there is no other point that may cause a problem.
In the practice, that means you'd need to have 129 words with a
common prefix (including empty string) but all different after
this. It's almost impossible with Google Keyboard since there are
only so many keys on the keyboard that you can make a word out
of, and then again you'd have to do it repeatedly until it
actually enters the user history dictionary, wait for it to get
saved on the disk.
The bad news is, if you manage to get this far, the keyboard will
crash every time and won't be able to get up until you clear
data for the package.
The good news is, the dictionary itself is not corrupted and only
the reading code is wrong. So updating to a newer version would
actually even recover from this situation.

All in all, considering how almost-impossible this is to trigger,
I don't think even a single user actually did hit this bug.

Bug: 8583091
Change-Id: Iabb2a7f47cbd9ed3193d2a3487318d280753e071

* commit 'a94bb198':
  fix assertion

Change-Id: I34ff470122aa0f34c66425d2eeae7590187d3074

Bug: 8284624
Change-Id: I14470bb2373965aefa921b2c94948450bfa438e3

* commit 'b12c2af3':
  Tighten unit test condition of MoreKeysKeyboardBuilder

Bug: 8601979
Change-Id: Icf584f3b35adce69cc3dfc46f3aacfef05e5dd2a

* commit 'dc64866c':
  Import translations. DO NOT MERGE

* commit '0dbc8c35':
  Import translations. DO NOT MERGE

* commit 'bfedad23':
  Import translations. DO NOT MERGE

* commit 'f2ab0adc':
  Import translations. DO NOT MERGE

Change-Id: I2cb68d3f0804a0c9990916a89e079510b465253f
Auto-generated-cl: translation import

Change-Id: I7c8b83b352dcc840ee2a8a6f0b8e6d4d28b4e08f
Auto-generated-cl: translation import

Change-Id: Ie74fdb8041ac5d7eb5d15a49f9aac834751cc9c2
Auto-generated-cl: translation import

* commit 'ededdc6a':
  Avoid NPE

* commit '128961ad':
  Fix failing tests

RichInputConnection#getWordRangeAtCursor may now returning
either a SpannableString or a String. We can't test that with
String#equals(), but TextUtils#equals() does the job for us.

Change-Id: I59ebe54207e92f4d90b49476b64f1e12fd4929cb

* commit '2cd1136b':
  Remove the dialog to insert words to the dictionary.

* commit '91bcf5eb':
  Restart suggestions when the cursor moves.

* commit '02ce3dc2':
  Fix a bug with bad application completions

Bug: 8561056
Change-Id: I91fb0ac76dabfc841bafc0e2c0ea9f63e6f604f9