| Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I226bb8e21fd2b2b6639896a1cc433d19f3f431c2
|
|
Change-Id: I15036545751abe751f2768daef7f3f1605a5457e
Auto-generated-cl: translation import
|
|
Change-Id: I6f88694633aa9f39c6b1731ea7634b80d3e3bf69
Auto-generated-cl: translation import
|
|
Change-Id: I04aed3599ff9570197b408a5d16ea48422294f97
Auto-generated-cl: translation import
|
|
Change-Id: I50e530351c75746759fefc4113c4f881755405ec
Auto-generated-cl: translation import
|
|
This is a very rare corner case.
Bug: 11072132
Change-Id: Iad2aa69511f7dc99105284a049c63f2f997b8ef0
|
|
This also includes a fix that allows this code to read surrogate
pairs in this processing.
Bug: 11070482
Change-Id: If5ef8d6863938252f09128b7e99ea07ece6e7019
|
|
Bug: 10538430
Change-Id: Ib11e29794216b54001806ab12fe440d157243dc1
|
|
Bug: 10538430
Change-Id: I91e03a8e7914628cdc8e57c124c95e5e6e8ea2a6
|
|
Change-Id: I5f85a7a0f94ea9ecbe0c4a8caebcf551fa9c9669
|
|
Change-Id: I403fc24a407fdd3b433d5820f1b46e6985cbe83e
|
|
Change-Id: I986ab26faf535fc4bc98443053f534eced9d048f
|
|
Bug: 10197478
Change-Id: Ib79cd3a81b01b16259df29b36e1df6b8f0affca8
|
|
Cherry pick of Ie2033b2f5253b2e2
Bug: 10954182
Change-Id: I9cc61e27a207055d5a43fe3da6fd1ec63bae49fd
|
|
Bug: 6669677
Change-Id: I0401a4c0908c702ce65abfa5e017dd16cb1296f9
|
|
Change-Id: I2208378b33038771b460abb33f9a690872e998e2
|
|
Change-Id: Ie69d84e090f69dc3ea1f5de73ad8c954ecd2c6a7
|
|
The new set of parameters are optimized for both
keystroke savings and regression test scores.
This change is corresponding to the patch 6 of
Change-Id: Ib8439a85de26cbbba58837344717f0acbfcf0ab0
in the regression test repository.
Here is the link to the doc analyzing the
“nnow → know” case:
https://docs.google.com/a/google.com/document/d/1XIHfAHLlP1f3F8R-u7yxPGWcP58tokygzN_lQKXFFgM/edit
Here is the link to the spreadsheet showing
the diff of the words with frequencies >= 10
in en_user_log_phones_2011_08.csv.
https://docs.google.com/a/google.com/spreadsheet/ccc?key=0Am_RQlV4zC6SdFFVTlhJT0RLUENCWWZOZ3JQTUpMQ2c&usp=drive_web#gid=0
Updated TRT Results for this change:
[Category diff]
+1 783
-1 717
+2 20
-2 34
+3 34
-3 20
+4 575
-4 777
+5 765
-5 755
+6 785
-6 666
+7 479
-7 472
[Weighted category diff]
+1 999
-1 965
+2 21
-2 35
+3 35
-3 21
+4 804
-4 980
+5 970
-5 971
+6 954
-6 831
+7 645
-7 625
Bug: 10613502
Change-Id: I5cd447673a196ad5af641a2118602bec879bdefb
|
|
Bug: 10538430
Change-Id: Ie2033b2f5253b2e2fc2229ba6c95568e7b2a58fa
|
|
Bug: 10920165
Change-Id: I340759eadbde7fb64cb3b9a3c619ee3a768cedf8
|
|
Bug: 6669677
Bug: 10667710
Change-Id: I6cdc6a6c9cacc7f276fda3a26ec31e3eb928471c
|
|
Bug: 10920165
Change-Id: I6372492e97297baad4c5aeeb3fb36dcccd7a944b
|
|
Change-Id: Ic586e46e5a9f59de53d53e59886d635345940974
|
|
Bug: 10964805
Change-Id: I862a6b920a7a09eac4e012bfe75f087b2d7b4fe6
|
|
Bug: 10964805
Change-Id: Ia3cd891d20aee2226092f0f646d8f280901786fc
|
|
Bug: 11032428
Change-Id: I5d422f1c15a582015770ef9a652348ca6eb8ab85
|
|
Bug: 10786040
Change-Id: I0de7d4923ea13b44adcf1f4ea456796cd02ef27b
|
|
Change-Id: I4fe48281caf9d3cf83effb19933d8f168967f950
Auto-generated-cl: translation import
|
|
Change-Id: Ifee5f65e8da896db6bce982db0c8cdcbb3f49902
Auto-generated-cl: translation import
|
|
BUG: 11042719,11021829
Change-Id: I27c80d1a2489843a16bd2b055d2ae81797492d1c
|
|
Change-Id: Ib33b27214e67378646e44f5b45bda298f960524f
|
|
Change-Id: Iaf1556fec194d17cb4318f2bdcc837f8d79449ef
|
|
Bug: 6669677
Change-Id: Ib465fa7e1a7f289a07843535ba89d0dd5259e803
|
|
Bug: 6669677
Change-Id: Ib5994a2e343dfcdaf23755e523f52846709b1c6c
|
|
Bug: 6669677
Change-Id: Ib2d9228b951c77dab7a8675ce9db60677e87e771
|
|
What's happening here is, setAlphabetKeyboard sets the
keyboard to AUTOMATIC_SHIFTED and updates the keyboard, then
restoring the keyboard old state sets it back to UNSHIFTED without
updating it. When we finally know what the correct value is,
we try to set it to UNSHIFTED, but since that's already the currently
recorded state, it skips updating the keyboard forever.
The solution is to avoid setting the shift state without updating the
keyboard.
Bug: 10948582
Change-Id: Ic8670401e378f8284e851281f91a9ad93eac8e90
|
|
Bug: 10118761
Change-Id: Ia7d1c6c526dae849f447c26387e96a4fb4d6042f
|
|
Bug: 6669677
Change-Id: I97839b2184b95ae1659c55a9b31d22e2d601cba1
|
|
Bug: 10920165
Change-Id: Ie9008452ee292fb0b1fec66e2ffed228c4af6c3e
|
|
When there are too many bigrams, we stop reading the file,
so the file pointer is in an inconsistent place. This means we
have no idea what's going to happen next. It's better to crash
right away.
Change-Id: Id3b7b78cbe4fda3493b3c9c46758763e1ab5f6a3
|
|
Bug: 10612450
Change-Id: Ie0ae953958d2b0a0a4da651584f1e28b0ba38ae3
|
|
I think I may pass out from the sheer ugliness
Change-Id: I1e709f03ef47ec713552d41fd9e37e01b810ae88
|
|
Bug: 10923117
Change-Id: I27ba38e5f388cc15ae331fd05d63db4e4a41cbbf
|
|
Bug: 9059617
Change-Id: I066abf018df5aaeabf415425dd822ebe233e6008
|
|
Change-Id: I94c394f45f2717bc1a4b95692a5757c1e7179152
|
|
Change-Id: I419c3c119eb1e4d2e877c8c00564e46f40b6abc2
|
|
bug: 11003945
Change-Id: If9ff0487ebbb1c25c8b13eaa55615255921c61c6
|
|
Bug: 6669677
Change-Id: I9d6aba76cef2616f0549e612db9701e1d6a19467
|
|
Change-Id: I90f0ffed57f0efa9f01adb969fd499e2dcd2a0dc
|
|
Change-Id: I042ff041b68572182c87dc87db6a6aa2bbbefc6c
|