Change-Id: I51c5247ac925a158facb79057f704b763b903552

Change-Id: I849cec7deb5607e8ce8fb25c1f903f15328fb611

The symptom : when text is selected and the device is rotated,
sometimes the keyboard sets the word as being composed around
the start of the selection. Upon the next rotation this ends up
with the keyboard committing some text in place of the selection.

The cause : another bug in the framework with rotation >.>
The keyboard receives a call to startInput with a wrong cursor
position, namely one that does not represent a selection. The
keyboard sets a composition according to this wrong data. When
the keyboard is rotated again, it commits the text, which takes
the place of the selection.

The solution : actually when restarting input the keyboard
realizes that the cursor position is wrong. We cancel composition
at that time.
For robustness, this change also implements two other defensive
changes : upon call to onUpdateSelection, we actually realize
that the previous values were wrong, so we also fix it at that
time, and in addition, when rotating, we finishComposingText()
instead of commitText() which is less dangerous. Implementing
this later change also allows us to let less internal variables
from InputLogic escape to LatinIME, so it's also a good change
for design.

Bug: 14140799

Change-Id: Ib10de18e53e376ac1bbc8487e13d969828483346

Bug: 13142176
Bug: 15428247
Change-Id: I93b44ef40cafb6b811c68fa79f3a4971fc3916a5

Change-Id: I434cf507e68349b9893ac084645986d6b3d7da91

Bug: 13142176
Bug: 15428247
Change-Id: I2ae25090b67ad0c6df97dec7712e2f7e0bb08c40

Change-Id: I4f13e85a3db1ba4adf36c596cb23827bdcf93ae7

Bug: 12491371
Change-Id: Ib01452b6a2a53faa591b05e62014f356e0511308

Bug: 12491371
Change-Id: Ib1fc8affbccfbaca3424ecdc2812f47047106aa2

Bug: 13869301
Change-Id: Icd77a308f85cc16dccffe65a532471c738d6fbc5

Bug: 12491371
Change-Id: I8c5b1e91f41146a023edcc405e6120c0bf33f49b

Bug: 13283555
Change-Id: Iab0466425dc44779d110f2cd29d725d22eb04827

Rename `initialize' to `start' and `deactivate' to `stop' for ease
of understanding. It's completely bizarre that you can "deactivate"
a recapitalization and that will just restart a new one the next time
you press shift. Start and stop are easier to understand.

Change-Id: I455175aebfcfe11198c6c61bf2c6b19efc3f82df

It turns out passing hover event to accessibility key handling methods
isn't necessary. This parically reverts I1f7feef707.

Bug: 12491371
Change-Id: I9d71cd29723344433427795e44cb22ac41faace6

BUG: 14324207
Change-Id: Idc8582655bc73cb24e416e8ba78470209b2ff702

This CL reorders keys around the spacebar.
- On phone's symbols and symbols shift layout, the comma key is moved
  to the left of the spacebar to aligned with main layout.
- On tablet's layout, the comma key is moved to the left of the
  spacebar on all layout to aligned with the same layout of
  phone's. Also the comma key has "settings" as more keys.
- In Arabic and Perisan, the comma key of tablet already has some more keys
  This CL remove "/" and add "settings" instead.

Bug: 15281451
Change-Id: I6e0e75e4d4abfb1f356e7499be91424c7c57c58b

Enrich the dictionary with many words generated from stems
extracted from the dictionary and rules written by hand.
This adds 45,619 words to the dictionary. Hopefully, almost none
of them is incorrect, though a lot are not very common.

Bug: 8010862
Change-Id: I51c7ebd16ff859ec1e765b0604dd1cfca159ab08

Change-Id: I2cba2bb5b2f449ed29895365b9c6ca285a7640fe

KeyboardAccessibilityDelegate.synthesizeTouchEvent() wrongly passed
pointer's id as a 6th argument of MotionEvent.obtain method that
should be metaState.

Change-Id: I822f9647a1ba27ee8cee39f373f6a1c003ebf665

Change-Id: I913ec290ddfd0ae4cc6e600ba95b7442167f0989

Change-Id: I0ef983f54e828193e9c7e4a10c888f72702d499c

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

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