You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I build a single dictionary at the top of the list of scoring filters for all configs I provide. This makes a lot of sense, since virtually all other dictionary entries would match the syllabic filter anyway, making it largely ineffectual to move any specific dictionary to another scoring position. However, both the corpus config and pref config have length minimums on the syllabic and alphabetic matches- meaning that it would matter for short words (1 or 2 characters) that don't appear in the dictionary placed in the first position.
Now, the trouble is that there are pretty few candidates for benefitting from this change. po, te, to, and wa out of linku obscure, and a fair number more out of the sandbox. The value of a change like this is... small. Maybe not even worth it.
The text was updated successfully, but these errors were encountered:
gregdan3
changed the title
Explore placing less common dictionary words in lower-scoring positions in the Corpus and Pref configs
Explore placing less common dictionary words in lower-scoring positions in the Pref config
Aug 14, 2024
Currently, I build a single dictionary at the top of the list of scoring filters for all configs I provide. This makes a lot of sense, since virtually all other dictionary entries would match the syllabic filter anyway, making it largely ineffectual to move any specific dictionary to another scoring position. However, both the corpus config and pref config have length minimums on the syllabic and alphabetic matches- meaning that it would matter for short words (1 or 2 characters) that don't appear in the dictionary placed in the first position.
Now, the trouble is that there are pretty few candidates for benefitting from this change. po, te, to, and wa out of linku obscure, and a fair number more out of the sandbox. The value of a change like this is... small. Maybe not even worth it.
The text was updated successfully, but these errors were encountered: