009e02ce4a132b0f94d130c36761e18935577af1 |
|
29-Oct-2014 |
Adrian Velicu <adrianv@google.com> |
Further fixes to treat 0-frequency words Previously, when both legitimate 0-frequency words (such as distracters) and offensive words were encoded in the same way, distracters would never show up when the user blocked offensive words (the default setting, as well as the setting for regression tests). When b/11031090 was fixed and a separate encoding was used for offensive words, 0-frequency words would no longer be blocked when they were an "exact match" (where case mismatches and accent mismatches would be considered an "exact match"). The exact match boosting functionality meant that, for example, when the user typed "mt" they would be suggested the word "Mt", although they most probably meant to type "my". For this reason, we introduced this change, which does the following: * Defines the "perfect match" as a really exact match, with no room for case or accent mismatches * When the target word has probability zero (as "Mt" does, because it is a distracter), ONLY boost its score if it is a perfect match. By doing this, when the user types "mt", the word "Mt" will NOT be boosted, and they will get "my". However, if the user makes an explicit effort to type "Mt", we do boost the word "Mt" so that the user's input is not autocorrected to "My". Bug: 11031090 Change-Id: I92ee1b4e742645d52e2f7f8c4390920481e8fff0
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
6da9b21191dc7d6049d96945366ec7e605e716e6 |
|
12-Sep-2014 |
Jean Chalard <jchalard@google.com> |
[ML8] Add a language weight ...and rename an improperly named normalization value Bug: 11230254 Change-Id: I0f5633148a9f66dbfd7d28540b8a8985131c4549
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
ed1ab3b3632d7fd366a33944abf1e2d7f9ad6539 |
|
15-Aug-2014 |
Keisuke Kuroyanagi <ksk@google.com> |
Improve accent error handling in exact match logic. Bug: 16963362 Change-Id: I50a48806bc3147388d165faab6b572415a851f29
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
5b69472d56eaebecab772012b5a590c5c9ce7511 |
|
31-Jul-2014 |
Keisuke Kuroyanagi <ksk@google.com> |
Remove doesAutoCorrectValidWord(). Possibly offensive words are wrongly demoted when input by gesture. Change-Id: Ibb2eb73d4191dea6cb767643341fe96465c1f70c
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
d73edf23aca59e6a0a83a79cf24db3850ef473ff |
|
27-Mar-2014 |
Keisuke Kuroyanagi <ksk@google.com> |
Use SuggestionResults to get suggestion. Bug: 8187060 Bug: 13333066 Change-Id: I435096ecf8422453f9b167adb0ca3b9c8a840018
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
622589ab431b397fad69edb7d9057335ca7475e9 |
|
14-Mar-2014 |
Ken Wakasa <kwakasa@google.com> |
Several cleanups Remove obsolete comment and unused macros. Cosmetic fixes as well. Change-Id: I9843331c8ce90d9b10b54f425ea1c7416b57c541
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
a000a32c8094d0dec453b0cebf748a089b0ad39a |
|
13-Feb-2014 |
Keisuke Kuroyanagi <ksk@google.com> |
Fix reading uninitialized memory. Bug: 12967899 Change-Id: Ia17e4ca9dd8c1e0b24b0fb7e73d07b97c5d81c0c
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
54622d38c246cb5b2ccb24c6756df25b0ce730f4 |
|
04-Feb-2014 |
Keisuke Kuroyanagi <ksk@google.com> |
Don't boost exact matches for personalized dicts. Bug: 12800726 Change-Id: Ia3a2f82db6cdc9645cad0e329c0b79328d7452cc
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
21e2380234f5f2bf069239e76b0fa8758b67b6a7 |
|
28-Jan-2014 |
Keisuke Kuroyanagi <ksk@google.com> |
Improve the double letter word promotion logic. The old logic only checks the top 3 suggestions before the final adjustment. It leads to instability in scores. Bug: 10700674 Change-Id: I986aed2aefd66c1fba6196a8f100fcb5bc838a38
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
afa6c07d30193e5ba221a53f7670a5c4e2f635d1 |
|
18-Dec-2013 |
Keisuke Kuroyanagi <ksk@google.com> |
Differentiate exact matches' minor errors. Bug: 8844931 Change-Id: I06754643188ccd28ba8c873878f7761787d91ff6
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
9ee90955287d616158ad4cf099c4772f58c16942 |
|
18-Dec-2013 |
Keisuke Kuroyanagi <ksk@google.com> |
Move methods for scoring from Traversal to Scoring. Bug: 8844931 Change-Id: I6137d06e597f4e7b81aaf29555199e18984f2c39
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
b179199830d198473154cfe56b3d712966a16c6f |
|
22-Jul-2013 |
Keisuke Kuroynagi <ksk@google.com> |
Fix: huge bigram costs for blacklisted words. Bug: 8844931 Change-Id: I523005c5ed9a3d401a67b0e4e1c3ff2e4574e6df
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
b68e73448104714e8f12f89a1e00fb10b5fd14c4 |
|
08-Apr-2013 |
Ken Wakasa <kwakasa@google.com> |
Cleanup the include paths Change-Id: Ic93d39e230170cfc9f5be6d81d42006e1a61e347
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|
a6a416519603d2e65416dd8f9507913b7e4fd0a0 |
|
02-Apr-2013 |
Satoshi Kataoka <satok@google.com> |
Move typing policy to AOSP Bug: 8197301 Change-Id: Ife9b41a465d7b8d707623a6d3e4c1c88c3c3c4ab
/packages/inputmethods/LatinIME/native/jni/src/suggest/policyimpl/typing/typing_scoring.h
|