Bug: 8689880
Change-Id: I908c22d362f2f6f07e5e04be14d3aaa749a8ac8e

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

bug: 8662567
Change-Id: I1ac9b4b8834f3b0ea537ad3142fa533dea10f23e

Also, theoretically, we don't want to retrieve older suggestions if
there are no results for a recorrection - that would look random.
This bug addresses this too.

Bug: 8657919
Change-Id: I44f36d34a708a968ab71fa0592da57f4c97d4b7f

Bug: 8657736
Change-Id: I459d1c200826c1c394f8207475ecf60a4f356793

What do you mean "Can't happen"?
It happens all the time - the empty string is the default ID, and it
needs to be updated like everyone else.

Bug: 8651858
Change-Id: I5a2f2ebb5b2ef08b27f26be8fb2c3d2f231ebcfc

Bug: 8344402
Change-Id: I41b8440f0d72a66fde3f6feb0db8239c9bb10ea3

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

Bug: 8556775
Change-Id: Ie12e0dc9bfeae45f6883580801e07d44be1d1d33

This is about as ad-hoc as it gets, but then again, what we want
is probably as ad-hoc as it gets.
All URL boxes I know of double as search bars, and not adding
automatic spaces there sucks (e.g. in Chrome URL bar).
And in other boxes actually you don't want to add a space if
it looks like a URL. QSB isn't even a search box, and it behaves
like this.

So I think this is actually the right answer to the problem.

Bug: 7062925
Change-Id: Ib09472b34644fd5bf2dc84bb97cedeeba28bcd02

Bug: 7167303
Change-Id: I8f76fe0aec6cb32388e7c85d04516d1dd7d28c29

Change-Id: Iafdbe305712c8a571f0f5abc2032df086d7ac015

Change-Id: Ibf2cdedf510c296561bb5eeb6ff18c3414d6d6f4

Bug: 7657025
Change-Id: I2f8fe7fc4596a498322ba5ccabbd0c18a2bc36cf

Change-Id: Ib4d002f90cd3a0e9ad4c04b883b0c1f05ada3ccf

Bug: 8620678
Change-Id: Ia91761f33518a010b2844d34523cadece261c67e

Bug: 8620758
Change-Id: I39f07939ebb6148a48aae5b915ee807002a5b02d

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

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

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

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

bug: 8589156
bug: 8588538
bug: 8588746

Change-Id: I14050dc3542946c1bae2e1dc8b63b99758d5f9aa

Bug: 8583091
Change-Id: I9195d68e44e9a282e25ccd2978d7b4088f600170

The only place where it's used is checked for nullity.
Also, it's possible, also difficult, to match a different
recapitalize with the old code, triggering a bug that
this fixes.

Change-Id: I717d6df489025c75d1caca290a9086c3b39a9306

Bug: 7980115
Change-Id: I8de31068992aec712eaad132857d9dc61f28e30a

>>> dictionaries/en_GB_wordlist.combined.gz
Header :
  date : 1366003032 <=> 1366021966
Body :
Deleted: FTP 88
Deleted: HTTPS 66
Added: www 72

>>> dictionaries/en_US_wordlist.combined.gz
Header :
  date : 1366003070 <=> 1366021978
Body :
Deleted: FTP 88
Deleted: HTTPS 66
Added: http 95
Added: www 71

>>> dictionaries/en_wordlist.combined.gz
Header :
  date : 1366003861 <=> 1366021987
Body :
Deleted: FTP 88
Deleted: HTTPS 66
Freq changed: http 120 -> 95
Added: www 71

>>> java/res/raw/main_en.dict
Header :
  date : 1366003861 <=> 1366021987
Body :
Deleted: FTP 88
Deleted: HTTPS 66
Freq changed: http 120 -> 95
Added: www 71

Bug: 8233807
Change-Id: Id55f6e0dcc9ddff26902c0857edcbb9b10d42328

Upon pressing Shift, if there is currently a selected string, have
Latin IME change its capitalization.
This does not yet have the keyboard mode follow the mode - the change
is complicated enough as is.

Bug: 7657025
Change-Id: I54fe8485f44e04efd72c71ac9feee5ce21ba06f2

Bug: 8084810
Change-Id: I1743c09c43ca6835bb2f607684b037bf17d36335

If the user gestures a word, then hits backspace in
disapproval, and gestures about the same thing again,
make sure that we don't suggest the same thing again.

Bug: 7549311
Change-Id: I793bc4df7c3841fa8f2f4146707c26e873f374c1

Bug: 8560722
Change-Id: I825b135bd13aca17e712330660978b834648dbc3

Bug: 8613600
Change-Id: I279d3264080aede59203205c45763c7f8ff08ae6

>>> dictionaries/en_GB_wordlist.combined.gz
Header :
  date : 1355802832 <=> 1366003032
  version : 29 <=> 31
Body :
Deleted: HTTP 95
Deleted: WWW 72
Added: mm 135

>>> dictionaries/en_US_wordlist.combined.gz
Header :
  date : 1355112451 <=> 1366003070
  version : 28 <=> 31
Body :
Deleted: HTTP 95
Deleted: WWW 71
Added: mm 135

>>> dictionaries/en_wordlist.combined.gz
Header :
  date : 1355802851 <=> 1366003861
  version : 29 <=> 31
Body :
Deleted: HTTP 95
Deleted: WWW 71
Added: mm 135

>>> dictionaries/fr_wordlist.combined.gz
Header :
  date : 1357617878 <=> 1366003217
  version : 29 <=> 31
Body :
Not a word: re false -> true
Shortcut added: re le 15

>>> dictionaries/nb_wordlist.combined.gz
Header :
  date : 1355802836 <=> 1366003450
  version : 29 <=> 31
Body :
Freq changed: iPhone 91 -> 30
Added: app 30

>>> dictionaries/ru_wordlist.combined.gz
Header :
  date : 1358763720 <=> 1366003693
  version : 30 <=> 31
Body :
Freq changed: за 140 -> 181
Freq changed: не 140 -> 191
Freq changed: про 131 -> 151
Freq changed: эры 125 -> 140

>>> dictionaries/sv_wordlist.combined.gz
Header :
  date : 1355802856 <=> 1366003804
  version : 29 <=> 31
Body :
Added: vi 180

>>> java/res/raw/main_en.dict
Header :
  date : 1355802851 <=> 1366003861
  version : 29 <=> 31
Body :
Deleted: HTTP 95
Deleted: WWW 71
Added: mm 135

>>> java/res/raw/main_fr.dict
Header :
  date : 1357617878 <=> 1366003217
  version : 29 <=> 31
Body :
Not a word: re false -> true
Shortcut added: re le 15

>>> java/res/raw/main_ru.dict
Header :
  date : 1358763720 <=> 1366003693
  version : 30 <=> 31
Body :
Freq changed: за 140 -> 181
Freq changed: не 140 -> 191
Freq changed: про 131 -> 151
Freq changed: эры 125 -> 140

Bug: 8560415
Bug: 7556679
Change-Id: If1c628edcb1cc5efd67e1715acf94f19c0eb4643

Bug: 8284624
Change-Id: I839d7a769d98f29be647dbe511ba3f73ca44446d

Bug: 8605150
Change-Id: Iadbebfb80e765c97e58e8524eb87419f2a9e41d4

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

Bug: 8284624
Change-Id: I14470bb2373965aefa921b2c94948450bfa438e3

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

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

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

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