Keeping in sync with Plover
didoesdigital opened this issue · 2 comments
Plover removes bad strokes and adds useful suggestions irregularly from comments in this issue: Dictionary Suggestions #400.
Keeping dict.json in sync with Plover's main.json may help newcomers learn from Typey Type for Stenographers without Plover's misstrokes as well as keep up with Plover's main community dictionary. If they get far out of sync, it will be harder for beginners to understand what strokes to use, why certain translations exist, and have a harder time choosing between them.
The current practice for Plover developers is to delete comments on the suggestions thread as they get merged to the dictionary. To preserve the history of those comments and reasoning for dictionary changes, we might continuously commit changes, referencing the original comments.
To avoid getting ahead of releases of the Plover dictionary with Plover app releases, we could hold back the changes here on a separate branch. When a Plover version is released with a dictionary update, we can merge the branch back into master. Meanwhile, anyone that wants the bleeding edge dictionary can use the branch dictionary.
No releases of the Plover app have been made. The open PR has conflicts almost beyond repair. This approach needs rethinking.