Closed ksqsf closed 3 months ago
I'm confused why the speller only considers table and user_table in the first place.
If there's a good reason, alternatively, we can make history_translator always tag candidates as "history".
Somewhat related: I think we should also support script_translator
.
Somewhat related: I think we should also support
script_translator
.
The auto-select feature comes from table-based IMEs. I'm not sure if the feature works with script_translator
because the latter always enables sentence input, therefore you can hardly tell when the input is done and cannot be any longer.
Pull request
Previously, the speller only auto-selects Phrases (type "table" and "user_table"), and does not select SimpleCandidate, but history_translator only produces SimpleCandidate, and thus history candidates cannot be auto-selected. This PR corrects this oversight.
(
history_translator
will preserve the old candidate type, e.g. "uniquified", but we cannot access the genuine candidate via SimpleCandidate here, unfortuantely.)Issue tracker
Fixes will automatically close the related issue
Fixes #
Feature
Describe feature of pull request
Unit test
Manual test
Code Review
Additional Info