-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Divvun sme keyboard not showing spelling suggestions #6
Comments
Drastic things must have happened to the spelling suggestion mechanism. The sme keyboard now in 9 out of 10 cases presents irrelevant suggestions. For "Anár" (above) it suggests It seems the whole system is just broken, drawing accidental candidats from the hat. To the extent that anything is working here, neither Levenshtein nor frequency seem to be in place, let alone any tailored suggestion mechanisms (neighbouring letters, e.g.). More data: Input is wrong, correct in parentheses: Input is correct: |
It is possible that speller downloads are still turned off, due to the bug in the SJD keyboard that totally locked the phone when trying to download a non-existing speller. If that is the case, what you see might be entries from the user dictionary, since nothing else is available. Also, if this is the case, it is only visible on Android (iOS never had the SJD issue, so downloads were never removed). Try to check the speller on an iPhone or iPad, the actual speller file should be identical if available, and should thus behave the same. If it is not, it is due to factors outside the speller itself. |
My i-things are at home. I admittedly have installed the SJD keyboard (both sme and sjd from the non-dev version). But users not having installed SJD report the same as me: no relevant suggestions (and it has been so for quite a long time). If the problem is a non-existing sjd speller, would then adding the sjd fst (which is good enough to be useful) fix the problem, a problem that goes beyond sjd users? |
Android version 9 (Sony Zperia XZ1 Compact)
Divvun Keyboards version 3.1.0
The text was updated successfully, but these errors were encountered: