-
Notifications
You must be signed in to change notification settings - Fork 19
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
S*ELTD vs SELTD for "settled" #28
Comments
"SELTD": "settled", "SELTG": "settling", and "SELTS": "settles", can all be written without explicit entries using Plover’s orthography rules. We add explicit entries to condensed strokes to improve Typey Type suggestions and improve brief look ups. Fixes #28
@paulfioravanti It looks like The suffix key Then, using Plover's orthography rules, the second "e" is removed to give us "settled" as intended. I've added some explicit entries for settled, settling, and settles to improve look ups in Typey Type. Generally I try to limit the |
Thanks for highlighting this @paulfioravanti. Please let me know if any of that doesn't make sense. |
Thanks for the detailed explanation, @didoesdigital. That helps a lot! |
… in Top 10000 Project Gutenberg words, using orthography rules #28
The stroke entry for the word "settled" in Plover and Typey Type is
S*ELTD
. The word "settled" can also be stroked more easily without the asterisk asSELTD
(which I found out by accident).However, there is no specified entry for this stroke in any dictionary in Typey Type or Plover. Is there a reason for this that you can think of? If not, would this entry be worth adding to the Typey Type dictionaries as an improvement on the Plover entry?
The text was updated successfully, but these errors were encountered: