Merge lp://qastaging/~michael-sheldon/ubuntu-keyboard/fix-1347796 into lp://qastaging/ubuntu-keyboard
Proposed by
Michael Sheldon
| Status: | Merged |
|---|---|
| Approved by: | Bill Filler |
| Approved revision: | 236 |
| Merged at revision: | 245 |
| Proposed branch: | lp://qastaging/~michael-sheldon/ubuntu-keyboard/fix-1347796 |
| Merge into: | lp://qastaging/ubuntu-keyboard |
| Diff against target: |
141 lines (+65/-0) 7 files modified
plugins/pinyin/src/chineselanguagefeatures.cpp (+5/-0) plugins/pinyin/src/chineselanguagefeatures.h (+1/-0) plugins/westernsupport/westernlanguagefeatures.cpp (+5/-0) plugins/westernsupport/westernlanguagefeatures.h (+1/-0) src/lib/logic/abstractlanguagefeatures.h (+4/-0) src/lib/logic/wordengine.cpp (+48/-0) src/lib/logic/wordengine.h (+1/-0) |
| To merge this branch: | bzr merge lp://qastaging/~michael-sheldon/ubuntu-keyboard/fix-1347796 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Bill Filler (community) | Approve | ||
| PS Jenkins bot | continuous-integration | Approve | |
|
Review via email:
|
|||
Commit message
Calculate the similarity between the current user's input and the prediction candidate, if they differ too much make the user input the primary candidate for auto-completion.
Description of the change
Calculate the similarity between the current user's input and the prediction candidate, if they differ too much make the user input the primary candidate for auto-completion.
To post a comment you must log in.
Revision history for this message
| Michael Sheldon (michael-sheldon) wrote | # |
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | # |
review:
Approve
(continuous-integration)
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | # |
review:
Approve
(continuous-integration)
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
Are there any related MPs required for this MP to build/function as expected? Please list.
* No
Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes)
* Yes
Did you perform an exploratory manual test run of your code change and any related functionality on device or emulator?
* Yes
Did you successfully run all tests found in your component's Test Plan (https:/
* Yes
If you changed the UI, was the change specified/approved by design?
* No change
If you changed UI labels, did you update the pot file?
* No change
If you changed the packaging (debian), did you add a core-dev as a reviewer to this MP?
* No change