Difference between revisions of "Talk:Ideas for Google Summer of Code/Spell checking"
Jump to navigation
Jump to search
(Created page with " The speller should not give suggestions that aren't in bidix, since clicking "oh yes that's what I meant" and then it's not translated anyway, will just be frustrating. On th...") |
|||
| Line 1: | Line 1: | ||
| + | ==spelling vs trimming== |
||
| + | The speller should not give suggestions that aren't in bidix, since clicking "oh yes that's what I meant" and then it's not translated anyway, will just be frustrating. |
||
| − | + | On the other hand, the speller should use as large a lexicon as possible, so that we don't suggest bidix-words for words that are actually correct (but just happen not to be in bidix). One way of doing this in a space-efficient way would be to have an FSA where there are three possible states of finality: |
|
# not final, |
# not final, |
||
# correct but not suggest (words only in spelldix), and |
# correct but not suggest (words only in spelldix), and |
||
Latest revision as of 10:31, 13 February 2015
spelling vs trimming[edit]
The speller should not give suggestions that aren't in bidix, since clicking "oh yes that's what I meant" and then it's not translated anyway, will just be frustrating.
On the other hand, the speller should use as large a lexicon as possible, so that we don't suggest bidix-words for words that are actually correct (but just happen not to be in bidix). One way of doing this in a space-efficient way would be to have an FSA where there are three possible states of finality:
- not final,
- correct but not suggest (words only in spelldix), and
- correct and suggest (words that are in bidix).
