Bug: 8911672
Change-Id: I5d5635949530a67f95e5208986907251b7bce903

Bug: 12602903
Change-Id: I6835dee8bf8b356f0f1cf6c0531bee5b3415a13f

Bug: 12602903

Change-Id: I1ea4e558b6d2fde425ce28226647ad60095e3488

Removed an unused method too.

Change-Id: Id364009fd4e94ec65862fc3651a181e862909a42

Missing change after a thousandth comment fix

Change-Id: Iec48f892978507fb9823236cd1c5a70209b58b0e

This is a followup to IL69.

Change-Id: Iba154517aa7f75b9f16aa1b808c0da8d84be837f

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

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

Change-Id: I382abd3104d535a1e868935d8cfb4e34ad8ebaed

This constant is better located in SuggestedWords.
Or it could be in Constants, that would be fine too.

Bug: 8636060
Change-Id: I3e721bb1e2559f028dce8929eceadfe0478c5924

Followup to IL66

Change-Id: I067e72c36f483cc3e3b24736c01843531298b507

Please hold my gun while I have this nice cup of tea.
Yes !!

Bug: 8636060
Change-Id: I33c8ffe51bb2106b17f7941235ad1e427e3a81f7

Bug: 8636060
Change-Id: Iec56bce362ebfc52fedab02b127978abb4f3c7f9

Bug: 8636060
Change-Id: I624a45500603dfad355ee3b8b794b2d895219c0b

Bug: 8636060
Change-Id: I242b7c264abf380bcd6b6b3c848238921f988e54

This is necessary for tests

Bug: 8636060
Change-Id: I50ea401a22e4df72333eda61ca39aa180966ee4b

Bug: 8636060
Change-Id: Ib13a54854e30afb79217a0a1f2aeca50a95ba155

Bug: 8636060
Change-Id: I3b144993e2bcd552f9b292b8f057c9db4216125c

This works because getKey{X,Y} is a no-op on
Constants.NOT_A_COORDINATE.

Bug: 8636060
Change-Id: I2f7dd96b6011f094110f7978f8ff24ef2a6e2585

Bug: 8636060
Change-Id: Ic051e5d5514d270101b0571a2d30e2caa8f85bc1

This also fixes the coordinates passed to logOnDelete and
log onSeparator.

Bug: 8636060
Change-Id: I4703d61ad7de76b501adca18df3a69e06450c9a1

This is fine because getKey{X,Y} is idempotent for any
non-keyboard coordinate value.

However this makes a net change : the x,y values passed to
LatinImeLoggerUtils.onNonSeparator are now different.
The point is however that they used to be wrong. The logged
values used not to account for the keyboard padding that
is present on tablets, and in the simulating tools we don't
know about that padding so we couldn't use the coordinates.
The catch here is that other calls like LoggerUtils.onSeparator
should follow suit, but this is too big a change to do it at once.
Follow-up changes will fix them too.

Bug: 8636060
Change-Id: If4b3d3cb1ed4b44c35f23e66aba3b5797236bba7

Change-Id: I03e5c8f95cb22c7096ff545f1181f914b80a6c58

Change-Id: I4103541d99fe59bfcf12379a1298a0a690497846

The newline string resource "\n" doesn't work off-device simulation.

Bug: 12623502
Change-Id: I3ad63d8afe50be174493d43f00f7191062c87cb7

Change-Id: I78d488ad84a11af809ee1f8d3d2fa01a89fbfa28

Change-Id: Ic7d2cbb2c1b2deaa4e735484bdc7413c0b3b1939

Change-Id: I2d2d226e21a46239077394ab09db88a4bd563460