Sorry, this issue was a fat-finger mistake...

In the current dict.json file, there are the following strokes for the word "editor", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"ED/EUT/O*R": "editor",
"ED/TOR": "editor",
"OERTD": "editor",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "editor" used is:

Plover would now seem to have two more entries for "editor" that are not currently in the dictionaries:

editor:
   ERTD
   ETD/O*R

I think the ERTD stroke should be added to the dictionaries and should be the stroke used in Typey-Type due to less mental overhead when it comes to the inversions ie I only have to think about RT after D, rather than also having to think about O after the word has finished (if that makes sense...).

Anyway, what I would like to propose is:

• Addition of "ERTD": "editor" (and "ETD/O*R": "editor"?) to dict.json
• Change "editor" stroke entry in top-10000-project-gutenberg-words.json from "OERTD": "editor", to "ERTD": "editor".

In the current dictionaries, there are the following entries for the word "civilisation":

In what I see as an extremely unfortunate oversight, Plover release weekly-v4.0.0.dev8+66.g685bd33 does not have an entry for "civilisation" with an "s" 😞 S*EUFLGS instead outputs "syphilising".

So, I guess the options for changing the current entries could be a combination of any of these options:

For the nouns.json entry:

a) Changing the entry to "SEUFLGS": "civilization" (since there is no "civilization" entry in that dictionary
b) Remove it completely without replacing it
c) Change the "civilisation" entry to its finger spelling: KR*/*EU/SR*/*EU/HR*/*EU/S*/A*/T*/*EU/O*/TPH*

For the top-10000-project-gutenberg-words.json entry:

a) Change the "civilisation" entry to its finger spelling: KR*/*EU/SR*/*EU/HR*/*EU/S*/A*/T*/*EU/O*/TPH* (I'm putting this as the first option since this dictionary also has a "SEUFLGS": "civilization" entry, and I'm assuming that you won't want to remove the "civilisation" entry entirely to bring the dictionary word count to 9999 words)
b) Perhaps pick another word to substitute for this word, as the "civilisation" finger spelling is a long one (I would have questioned whether it was normal to have different regional spellings of the same word in the top-10000-project-gutenberg-words.json dictionary, but then I saw that there are separate entries for words like "color"/"colour", "favor"/"favour" etc)

What would be a good compromise in this case?

The nouns.json dictionary has grown over the years in multiple directions e.g. chunking up the main Plover dictionary, adding "condensed strokes" before I gave that its own dictionary, and potential "new words" to include like "celeriac". Sometimes it causes problems as shown in #96.

Improvements

• Move "condensed stroke" style entries into condensed-strokes.json.
• Create a new new-nouns.json dictionary for new words to suggest for Plover that is not used in the Typey Type set.
• Reduce the dictionary down to only nouns that have been chunked out from dict.json as a means of organising and categorising the Plover dictionary.

In the current dict.json file, there are the following strokes for the word "picked", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"PEUBG/-D": "picked",
"PEUBG/-DZ": "picked",
"PEUBGD": "picked",
"PEUBGTD": "picked",
"PEUGD": "picked",
"TPEUBG/-D": "picked",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "picked" used is "PEUGD": "picked", and I'm wagering that this is the stroke that came up for me on Typey-Type.

Even though "PEUGD" is the shortest Plover-recognised stroke for "picked", I would have expected to see "PEUBGD" instead, with the full BG stroke for "k" (although, it does also sound "right" having a "g" sound substitute for a "k" sound). So, my question is: is PEUGD a mis-stroke for PEUBGD (and hence the entry in the Gutenberg dictionary should change), or is it fine as it is?

In Plover release weekly-v4.0.0.dev8+66.g685bd33, it would seem that there is no entry for "mare", but there are two entries in the dictionaries:

The entry for the stroke PHAEUR resolves to "mayor" in Plover, so having a look at the current Typey-Type dictionary strokes for "mayor", I can see:

but, the stroke PHA*EUR resolves to capitalised "Mayor" in Plover.

So, I guess I'd have the following questions:

• Since "mare" is in the Project Gutenberg dictionaries, I assume you want to keep it, so should the stroke for that entry perhaps be changed into the fingerspelling of "mare", and a new "PHAEUR": "mayor" entry added to dict.json?
• For the "PHA*EUR": "mayor" entries, should the stroke be changed to PHAEUR for "mayor", or should the entry be changed to be capitalised "Mayor"?

In the current dict.json and top-10000-project-gutenberg-words.json dictionaries, the entry for "diseased" is:

"STKAOEFD": "diseased"

However, there does not seem to be a stroke entry for "diseased" at all in in Plover release weekly-v4.0.0.dev8+66.g685bd33.

I'm assuming that to fix this issue in the dictionaries, "STKAOEFD": "diseased" should be added to bad-habits.json, but I'm not entirely sure what would be a good stroke to replace it with in dict.json and top-10000-project-gutenberg-words.json:

• Fingerspelling? (TK*/*EU/S*/*E/A*/S*/*E/TK*)
• Two-stroke? (STKAOES/-D, to be similar to the "STKAOESZ": "diseases" entry in top-10000-project-gutenberg-words.json)
• Something else...?

In the current dict.json file, there are the following strokes for the word "violation", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"SRAOEU/HRAEUGS": "violation",
"SRAOEUL/AEUGS": "violation",
"SRAOEUL/HRAEUGS": "violation",
"SRAOEULGS": "violation",
"SREU/HRAEUGS": "violation",
"SROEULGS": "violation",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "violation" used is:

Although Plover says it's a valid stroke, I feel that "SRAOEULGS": "violation" with the elongated "ī" sound (AOEU) is a more accurate entry pronunciation-wise, and so would like to propose:

• Changing the stroke for "violation" in top-10000-project-gutenberg-words.json from SROEULGS to SRAOEULGS

Line #148 of README.md should change from

- `"PHRAOBG": "{PLOVER:LOOKUP}",`: opens Plover’s add translation window

to

- `"PHRAOBG": "{PLOVER:LOOKUP}",`: opens Plover’s lookup window

In the current dict.json and top-10000-project-gutenberg-words.json dictionaries, the entry for "continues" is:

"T-PBS": "continues"

However, there does not seem to be a specific stroke entry for "continues" at all in in Plover release weekly-v4.0.0.dev8+66.g685bd33.

I'm assuming that there was an entry of "T-PBS": "continues" in the past that has since been removed, or that it's perhaps a typo for "T-PB/-S": "continues"(?).

The current output for T-PBS is "continuous". The current dict.json dictionary entries for "continuous" are:

"KOPB/TEUPB/KWROUS": "continuous",
"KOPB/TEUPB/OUS": "continuous",
"KOPB/TEUPB/WOUS": "continuous",
"KOPBT/KWROUS": "continuous",
"KOPBT/WOUS": "continuous",
"T-PB/KWRUS": "continuous",
"T-PB/WOUS": "continuous",

All of these would seem to be valid in Plover except for "KOPB/TEUPB/KWROUS": "continuous", which does not seem to be present.

The current stroke used in top-10000-project-gutenberg-words.json for "continuous" is:

Given that T-PBS outputs "continuous", I'm assuming this top-10000-project-gutenberg-words.json entry should be changed to its simpler stroke.

So, given all this, I'm not entirely sure of the correct courses of action, but perhaps something like:

• Change "continues" stroke entries in dict.json and top-10000-project-gutenberg-words.json from T-PBS to T-PB/-S (or whatever is the more appropriate stroke)
  • (Should "T-PBS": "continues" go into bad-habits.json...?)
• Add "T-PBS": "continuous" to dict.json
• Remove "KOPB/TEUPB/KWROUS": "continuous" from dict.json
  • (Add "KOPB/TEUPB/KWROUS": "continuous" to bad-habits...?)
• Change "continuous" stroke entry in top-10000-project-gutenberg-words.json from T-PB/WOUS to T-PBS

The aim is to remove all the misstrokes from dict.json to give new stenographers greater confidence in learning new briefs.

The first step is to remove all the misstrokes for the shortest available brief for every word, starting with words appearing in Typey Type's top 10,000 words lessons. If there’s a misstroke in a longer word, it is less likely to be suggested by Typey Type or dictionary look up tools.

The same misstrokes may appear in top words dictionaries and Australian English dictionaries and ought to be removed from them as well.

In the current dict.json file, there are the following strokes for the word "clutch", both of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"HRUFP": "clutch",
"KHRUFP": "clutch",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "clutch" used is:

Even though "HRUFP" is the shortest Plover-recognised stroke for "clutch", I would have expected to see "KHRUFP" instead, with the added K stroke for "c". So, my question is: is HRUFP a mis-stroke for KHRUFP (and hence the entry in the Gutenberg dictionary should change), or is it fine as it is?

In Plover, the stroke for "clutched" is KHRUFPD, which further makes me think this could be a candidate for bad-habits.json.

In the current dict.json file, there are the following strokes for the word "blast", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"PWRAFT": "blast",
"PWHRA*S": "blast",
"PWHRAFT": "blast",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "blast" used is "PWRAFT": "blast", and this is the stroke that comes up on Typey-Type.

Given that PWRAFT is missing the H for the "L" stroke, and given that it seems that every other dictionary entry that has "blast" as part of its word uses the full PWHRAFT stroke, I looks to me that PWRAFT may be a mis-stroke.

If that is the case, I'd like to propose:

• Moving "PWRAFT": "blast", to bad-habits.json
• Changing the entry in top-10000-project-gutenberg-words.json to PWHRAFT

The strokes for "groups" in Plover release weekly-v4.0.0.dev8+66.g685bd33, and in the repo dictionaries, are:

TKPRAOUPS
TPWRAOUPS
TKPWRAOUPS
TKPWRAOUPLS

However, in this repo, TPWRAOUPS is marked as a mis-stroke:

This makes sense to me, as it's missing the K to make up the full TKPW stroke for "g". Given that, I would also like to propose that:

• TKPRAOUPS also be moved from dict.json to misstrokes.json, since it's missing the W in TKPW for "g"
• The entry for "groups" in top-10000-project-gutenberg-words.json
  

  steno-dictionaries/dictionaries/top-10000-project-gutenberg-words.json

  Line 3225 in 69fc1df

  "TKPRAOUPS": "groups",

  
  changed to TKPWRAOUPS

Currently in the dictionaries, there are entries for "KRO*PL": "com" in:

However, in Plover release weekly-v4.0.0.dev8+66.g685bd33, there is no entry for lowercase "com".

The stroke KRO*PL, as well as KROPL, resolve to {^.com}. There is are entries for KROPL in these dictionaries:

There is also an entry in the UX-Design dictionary for KROPL as the standalone string ".com", though I'm guessing this is a conflict with the other dictionaries, and is now incorrect:

The only entry in Plover that is closest to a "com" standalone string is the uppercased version: "KO*PL/KO*PL": "COM".

Based on this what changes should be made to the dictionaries? I'm assuming that:

• "KROPL": ".com" in the UX dictionary should be changed to "KROPL": "{^.com}"
• "KO*PL/KO*PL": "COM" entry should be added to dict.json, and the existing "KRO*PL": "com" entry in dict.json should be changed to "KRO*PL": "{^.com}"

But with regards to the "KRO*PL": "com" issue in top-10000-english-words.json, what should the entry change to? "KROPL": "{^.com}"? "KO*PL/KO*PL": "COM"? Perhaps the fingerspelling of "com" ("KR*/O*/PH*": "com")?

In the current dict.json file, there are the following strokes for the word "bless", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"PWHRES": "bless",
"PWHRESZ": "bless",
"PWRES": "bless",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "bless" used is "PWRES": "bless", and I'm wagering that this is the stroke that came up for me on Typey-Type.

Even though "PWRES" is the shortest Plover-recognised stroke for "bless", I would have expected to see "PWHRES" instead, with the full HR stroke for "l". So, my question is: is PWRES a mis-stroke for PWHRES (and hence the entry in the Gutenberg dictionary should change), or is it fine as it is?

In the dictionaries, there are entries for word "notre" in the following places:

Plover release weekly-v4.0.0.dev8+66.g685bd33 does not have an entry for "notre" outside of being part of the entry for "Notre Dame".

"notre" features in the top-10000-english-words.json list, so I'm assuming that the entry itself needs to stay in some form, but the potential questions around it I see are:

• It's not an English word (as far as I know), so is its inclusion in the top-10000-english-words.json list correct?
• If it is correct, then should the stroke be changed to finger-spelling (TPH*/O*/T*/R*/*E)?
• Should this entry be converted to "Notre Dame" (TPHORT/TKAPL)?

As a steno learner who is trying to gain as much muscle memory as possible by mapping key strokes to letters/sounds in my head, sometimes I'll come across entries in Typey-Type like:

"THRAOUD": "fluid",
"TPALT": "fault",
"HREBSZ": "lenses"

Each of these strokes is the shortest stroke for its word, but it would seem that they are also shortcuts.

What this means for me is that, for example, when I see THRAOUD for "fluid" come up, but I'm expecting TPHRAOUD with the full TP for the "f" sound, like I see with many other words, I inadvertently stop and wonder if this is an irregular or special stroke, and then test the word with the longer stroke I'm expecting, given how I'm pronouncing the word in my mind. If the more detailed stroke proves to be correct, I will mentally adjust to use that stroke in the future, since remembering shortcuts at is, for me at least, mental overhead that I don't want to deal with at this point.

My question is, therefore, should Typey-Type prioritise the shortest stroke for an entry in all cases, or should it prioritise consistency to help build muscle memory, and then when a beginner graduates to intermediate and above, they can then make their own decisions on whether they want to use shortcuts? The answer to this question could also help to inform future pull requests as well.

In the current dict.json file, there are the following strokes for the word "folds", both of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"TPOLDZ": "folds",
"TPOELDZ": "folds",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "folds" used is "TPOLDZ": "folds", and this is the stroke that comes up on Typey-Type. It came up for me in the same practice word set as singular "fold", which has the single stroke TPOELD.

It struck me as strange that the singular and plural of a word would have a different stroke for their "O" sounds, so I was wondering if perhaps:

• "TPOLDZ": "folds" is a mis-stroke, and should be moved into bad-habits.json?
• Regardless of whether TPOLDZ is a mis-stroke or not, should the entry in top-10000-project-gutenberg-words.json be changed to "TPOELDZ": "folds", to give it a symmetry with "TPOELD": "fold" ?

In the current dict.json file, there are the following strokes for the word "hedge", both of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"HEPBL": "hedge",
"HEPBLG": "hedge",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "hedge" used is:

Even though HEPBL is the shortest Plover-recognised stroke for "hedge", I would have expected to see HEPBLG instead, with full PBLG stroke for the "j" sound.

Given that:

1. The stroke for "hedgehog" in dict.json uses the full HEPBLG stroke:

"HEPBLG/HOG": "hedgehog",

2. It would seem that HEPBL doesn't look technically like a mis-stroke(?) since its also used for single-stroke "hedged", along with HEPBLG

"HEPBLDZ": "hedged",
"HEPBLGD/-D": "hedged",

I would propose:

• Changing at least the stroke entry for "hedge" in top-10000-project-gutenberg-words.json from HEPBL to HEPBLG
• Either, depending on your opinion:
  • Leave HEPBL-based entries in dict.json as they are
  • Move HEPBL-based entries ("hedge" and/or "hedged") to bad-habits.json

In the current dict.json file, there are the following strokes entries for words starting with "find", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"TPAOEUPBD": "find",
"TPEUPBD": "find",
"TPAOEUPB/TKER": "finder",
"TPAOEUPBD/*ER": "finder",
"TPAOEURPBD": "finder",
"TPAOEUPBD/ERS": "finders",
"TPAOEPBGD": "finding",
"TPAOEUBD/-G": "finding",
"TPAOEUPBGD": "finding",
"TPAOEUPBD/-GS": "findings",
"TPAOEUPBGDZ": "findings",
"TPHAOEUPBD": "find it",
"TPAOEUPBDZ": "finds",
"TPHAOEUPBD/T-S": "find that it's",

Most of these entries use the stroke AOEU for the "ī" sound in "find", and this would lead me to believe that perhaps entries that shorten that sound, like "TPEUPBD": "find" could be mis-strokes.

Entries that use the shortened "ī" sound (in different ways) for "find" are present in many of the entries in other dictionaries:

So, my questions are:

• Are strokes that use anything other than AOEU for "find*" mis-strokes, and hence should be moved tobad-habits.json?
• If so, should the entries in all the other dictionaries linked to above be changed to their AOEU-using counterparts?

Currently, the dictionaries have the following entries for "er" (a word which appears in Typey Type exercises, I'm assuming, meaning 'er...', the exclamation expressing hesitation):

dictionaries/dict.json
Line 16029: "ER": "{er^}"

In the Plover dictionary for release weekly-v4.0.0.dev8+66.g685bd33, the keystroke ER/SP-S outputs "er ands" or "erands", and the entries for "er" are listed as:

"ER": "{er^}"
"*ER": "{^er}"

Stroking just ER provides the "er" that would be needed for the Typey-Type exercises, so if I was to make a pull request, I think I would potentially:

• Change all ER/SP-S entries above to be just ER (or potentially remove the ER/SP-S "er" entries altogether if "er" here was not meant to mean the word "er", but rather the prefix or suffix)
• Add the *ER entry to dict.json

But, I'm not entirely sure, hence this issue. What would be the best changes to make for these dictionary entries?

The stroke for "brings" in Plover release weekly-v4.0.0.dev8+66.g685bd33, and in the repo dictionaries, is:

"PWREUS": "brings"

Although a much longer stroke, I would have expected to see:

"PWREUPBGS": "brings"

with the full PBG for the "ng" sound in "brings". PWREUPBGS does actually work as a stroke for "brings" in Plover, but looks like it's not "officially"(?) recorded as an entry in Plover.

I'm assuming that there's something in steno theory that I'm missing, so I'm not doubting the correctness of the dictionary entry here. But, if, by chance, this is an oversight, is this stroke worth perhaps adding to the Typey-Type dictionaries, even if in an "unofficial" capacity? Or, is this a question perhaps for one of the Plover repos? Or, am I just barking up the wrong tree?

In the current nouns.json and top-10000-project-gutenberg-words.json file (but not dict.json?), there is the following stroke for the word "tidings":

"TAOEUGD/-S": "tidings"

Unfortunately, this entry does not seem to exist in Plover release weekly-v4.0.0.dev8+66.g685bd33, nor does "tiding" singular.

So, my questions are:

• Should these two entries be changed to their fingerspelling (T*/*EU/TK*/*EU/TPH*/TKPW*/S*)?
• Should an entry/entries for "tiding"/"tidings" be added to dict.json?

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 as SELTD (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?

In the current dict.json file, there are the following strokes for words containing "arrive", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"A/REUF": "arrive",
"A/RAEUF": "arrive",
"A/RAOEUF": "arrive",
"A/REUFD": "arrived",
"A/RAOEUFD": "arrived",
"A/RAOEUFS": "arrives",
"AE/RAOEUFD": "he arrived",
"AS/RAOEUF": "{^s arrive}",

In the top-10000-project-gutenberg-words.json dictionary, there is an entry for "arrive", that uses the following stroke:

Although Plover says it's a valid stroke, I feel that "A/REUF": "arrive", (and "A/RAEUF": "arrive", for that matter) could be mis-strokes, and that "A/RAOEUF": "arrive", with the elongated "ī" sound (AOEU) is a more accurate entry pronunciation-wise.

Given that there is only one entry for "arrives" ("A/RAOEUFS": "arrives",) which uses the elongated "ī" sound, as well as the "AE/RAOEUFD": "he arrived", and "AS/RAOEUF": "{^s arrive}", strokes, I would like to propose standardising on the elongated "ī" sound by:

• Removing the following entries from dict.json:
  • "A/REUF": "arrive",
  • "A/RAEUF": "arrive",
  • "A/REUFD": "arrived",
• Adding the following entries to bad-habits.json:
  • "A/REUF": "arrive",
  • "A/RAEUF": "arrive",
  • "A/REUFD": "arrived",
• Changing the stroke for "arrive" in top-10000-project-gutenberg-words.json from A/REUF to A/RAOEUF

The dictionaries currently have a stroke entry for the word "quitted" here:

Regardless of "quitted" still being a valid past-participle of "quit", Plover release weekly-v4.0.0.dev8+66.g685bd33 does not have an entry for it, which is causing issues when it comes up in Typey-Type. Also, the current stroke for "quitted" in the dictionary, KWEUT/-D, results in "quited" being output.

Since there is no stroke for a {^ted} output in the same vein of "-D": "{^ed}", unless there is a way of stroking "quitted" some other way, I would think that the stroke for this entry would need to be changed to its fingerspelling. What do you think?

In the current dict.json file, there are the following strokes for the word "clean", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"KHAOEPB": "clean",
"KHRAOEB": "clean",
"KHRAOEPB": "clean",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "clean" used is:

Even though KHAOEPB is the equal shortest Plover-recognised stroke for "edge" (along with KHRAOEB) I would have expected to see the full KHRAOEPBstroke instead, with full strokes for the "l" (HR) and "n" (PB) sounds.

Given that:

1. "unclean" and "cleaning" in the Gutenberg dictionary use the full KHRAOEPB stroke for "clean"

2. The strokes for "clean" variations in dict.json use the full KHRAOEPB stroke

"KHRAOEPB/*ER": "cleaner",
"KHRAOEPB/-G": "cleaning",
"KHRAOEPB/ERS": "cleaners",
"KHRAOEPB/HREU/TPH-S": "cleanliness",
"KHRAOEPB/SKWRUP": "clean-up",
"KHRAOEPBD": "cleaned",
"KHRAOEPBG": "cleaning",
"KHRAOEPBL": "cleanly",
"KHRAOEPBS": "cleans",
"KHRAOERPB": "cleaner",
"TKHRAOEPB": "clean it",
"TKRAOEU/KHRAOEPB/*ER": "dry-cleaner",
"UPB/KHRAOEPB": "unclean",

Are KHAOEPB and KHRAOEB mis-strokes for KHRAOEPB (and hence their entries in the Gutenberg dictionary should change, as well as the entries moved to bad-habits.json)?

Plover release weekly-v4.0.0.dev8+66.g685bd33 would seem to have removed the word "spake".

"spake"-related dictionary entries are currently here:

Funnily enough, the removal of "spake" from Plover does not affect the entry "THUS/SPAEUBG/SA*R/THAOUS/TRA": "Thus Spake Zarathustra": this still resolves properly with SPAEUBG as "spake".

So, since "spake" is in the Project Gutenberg dictionary, I assume that it still warrants keeping, and therefore should the remaining strokes for the entries be changed to the finger spelling S*/P*/A*/K*/*E?

The briefs.json dictionary has grown over the years in multiple directions e.g. chunking up the main Plover dictionary, adding "condensed strokes" before I gave that its own dictionary, and potential new briefs to include like "expansion". Sometimes it causes problems as shown in #98.

Improvements

• Move "condensed stroke" style entries into condensed-strokes.json.
• Create a new new-briefs.json dictionary for new briefs to suggest for Plover that is not used in the Typey Type set.
• Reduce the dictionary down to only briefs that have been chunked out from dict.json as a means of organising and categorising the Plover dictionary.

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.

In the current dict.json file, there are the following single-stroke entries for the word "estimation", both of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"STEUPGS": "estimation",
"STEUPLGS": "estimation",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "estimation" used is:

Although Plover says it's a valid stroke, I am wondering whether perhaps STEUPGS is a mis-stroke due to it not having the full PL stroke for "m", which is what I would have expected for the word "estimation".

Given that:

Other two-stroke entries for "estimation" in dict.json use the full PL stroke for "m":

"STEUPL/AEUGS": "estimation",
"STEUPLT/AEUGS": "estimation",

I would propose:

• Removing "STEUPGS": "estimation" from dict.json
• Adding "STEUPGS": "estimation" to bad-habits.json
• Changing the stroke for "dealing" in top-10000-project-gutenberg-words.json from STEUPGS to STEUPLGS

In the current dict.json file, there are the following strokes for the word "amidst", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"A/PH*EUFD": "amidst",
"A/PH*EUS": "amidst",
"A/PHEUTDZ": "amidst",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "amidst" used is:

I know that as a general rule, Typey-Type prioritises entries without *, but I think this word could be marked as an exception due to the awkwardness of the A/PHEUTDZ stroke. Particularly, the pinky finger being technically responsible for stroking TDZ, which at least I've found very difficult to do without accidentally also pressing S (or should the thinking for this stroke be that the right ring finger should be temporarily re-assigned responsiblity for pressing T...?).

I would be happy to have the entry in top-10000-project-gutenberg-words.json be changed to either of the alternatives, but I would lean a bit more towards A/PH*EUFD, even though its a letter more than A/PH*EUS and a pinky reach for the D key, due to it slightly more conforming to my mental pronunciation of "amidst".

In the current dict.json file, there are the following strokes for the word "remaining", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"RAOE/PHAEUPBG": "remaining",
"RE/PHAEPBG": "remaining",
"RE/PHAEUPB/-G": "remaining",
"RE/PHAEUPBG": "remaining",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "remaining" used is:

Although Plover says it's a valid stroke, I feel that "RE/PHAEUPBG": "remaining" with the elongated "ā" sound (AEU) is a more accurate entry pronunciation-wise (and all the other entries use AEU), and so would like to propose:

• Removing "RE/PHAEPBG": "remaining" from dict.json
• Adding "RE/PHAEPBG": "remaining" to bad-habits.json
• Changing the stroke for "remaining" in top-10000-project-gutenberg-words.json from RE/PHAEPBG to RE/PHAEUPBG

Currently, in both Plover and in the repo dictionaries, the stroke for "father's" is TPA*ER/AES. This stroke is, of course, correct, but I'm just curious if I'm missing something with regards to how it is formed. What I mean by that is:

• TPA*ER outputs "fare", and then stroking AES transforms it into "father's"
• TPAER outputs "father", and then stroking AES after that, you get the same "father's"

I would have thought that TPAER/AES would be a better stroke for "father's" since:

• it removes a single keystroke
• the building blocks of "father" + "'s" = "father's" is, at least for me, easier than "fare" + "'s" = "father's"

Is there a steno logical rule I'm missing? If not, would this be a potential candidate for a PR to improve on the Plover entry for Typey Type?

In Plover Theory, the main way to write words ending in "-mp" is to end the stroke with *PL. Eg:

• HU*PL: hump
• PU*PL: pump

Currently, all the dictionaries in this repo would seem to use the StenEd convention of -FRP. Eg:

• HUFRP: hump
• PUFRP: pump

Is there a reasoning behind this, whether it be personal preference or otherwise? If there is no particular preference, would creating a PR that changes the strokes for words ending in "-mp" to use Plover Theory be of value?

While learning Plover, I internalised the *PL stroke for "-mp" and was surprised to see it in Typey-Type, but since both methods are valid I'd thought I'd open this issue to clarify.

In some of the dictionaries, the PHA*R keystroke is used for lowercase "march" (walk in a military manner), but PHA*R actually outputs titleised "March" (the month):

Is the entry for these dictionaries meant to be for the capitalised or lowercase version?

If lowercase, I'd propose a PR to change these entries to "PHAFRPB": "march".
If uppercase, I'd propose a PR to change these entries to "PHA*R": "March".

In the current dict.json file, there are the following strokes for the word "leading", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"HRAEGD": "leading",
"HRAOED/-G": "leading",
"HRAOEGD": "leading",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "leading" used is:

This entry can also be found in ux-design.json:

Although Plover says it's a valid stroke, I feel that "HRAOEGD": "leading" with the elongated "ē" sound (AOE) is a more accurate entry pronunciation-wise (and all the other entries use AOE), and so would like to propose:

• Changing the stroke for "leading" in top-10000-project-gutenberg-words.json from HRAEGD to HRAOEGD

Since "HRAEGD": "leading" is used in ux-design.json, which I'm assuming is more of a custom, opinionated dictionary, depending on how you feel about the "HRAEGD": "leading" entry:

• Add "HRAEGD": "leading" to bad-habits.json (specifically marking it as a mis-stroke)
  • Hence, changing the stroke for "completely" in ux-design.json from HRAEGD to HRAOEGD as well
  • And removing "HRAEGD": "leading" from dict.json
• Or, doing nothing

In the current dict.json file, there are the following strokes for the word "dealing", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"TAOELG": "dealing",
"TKAOEG": "dealing",
"TKAOEL/-G": "dealing",
"TKAOELG": "dealing",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "dealing" used is:

Although Plover says it's a valid stroke, I am wondering whether perhaps TAOELG is a mis-stroke due to it not having the full TK stroke for "d", which is what I would have expected for the word "dealing".

Given that:

Strokes using "deal" in every other entry in dict.json use the full TK stroke for "d":

"TKAOEG": "dealing",
"TKAOEL": "deal",
"TKAOEL/*ER": "dealer",
"TKAOEL/*ER/AES": "dealer's",
"TKAOEL/*ER/SH-P": "dealership",
"TKAOEL/*ERS/AE": "dealers'",
"TKAOEL/-G": "dealing",
"TKAOEL/ER/SHEUP": "dealership",
"TKAOEL/ER/SHEUPS": "dealerships",
"TKAOEL/ERS": "dealers",
"TKAOEL/KWREU/-S": "dealies",
"TKAOEL/KWREU/O*": "dealio",
"TKAOEL/KWREU/PWOB": "dealybob",
"TKAOELD": "dealed",
"TKAOELG": "dealing",
"TKAOELG/*ER": "dealer",
"TKAOELGS": "dealings",
"TKAOELS": "deals",
"TKAOERL": "dealer",
"TKELT": "dealt",
"TKWAOEL": "deal with",
"TKWAOELG": "dealing with",
"TKWAOELS": "deals with",

I would propose:

• Removing "TAOELG": "dealing" from dict.json
• Adding "TAOELG": "dealing" to bad-habits.json
• Changing the stroke for "dealing" in top-10000-project-gutenberg-words.json from TAOELG to TKAOELG

In the current dict.json file, there are the following strokes for the word "edge", both of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"EPBG": "edge",
"EPBLG": "edge",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "edge" used is:

Even though "EPBG" is the shortest Plover-recognised stroke for "edge", I would have expected to see "EPBLG" instead, with the added L for the full stroke for the "j" sound (PBLG).

Given that:

1. "edges" plural in the Gutenberg dictionary uses the full stroke

2. The stroke for "edge" variations in dict.json use the full EPBLG stroke

"*EPBLG/PHOPBT": "edgemont",
"EPBLG/ER": "edger",
"EPBLGD": "edged",
"EPBLGS": "edges",

Is EPBG a mis-stroke for EPBLG (and hence the entry in the Gutenberg dictionary should change, as well as the entry moved to bad-habits.json)?

I noticed that in the top-10000-project-gutenberg-words.json dictionary, the stroke for "toss" is TOSZ, while in dict.json it is TO*S.

In the Plover dictionary for release weekly-v4.0.0.dev8+66.g685bd33, "toss" can be stroked as TOS, which is currently reflected in other dictionary entries in dict.json using "toss"-related words like:

"TOS/-D": "tossed",
"TOS/-G": "tossing",
"TOS/-S": "tosses",

However, in dict.json, the entry for TOS is "TOS": "{^s to}".

So, my questions are:

• Is the "TOS": "{^s to}" entry still correct?
• If it is not, is it worth attempting to standardise "toss"-related entries to use the easiest-to-stroke TOS (versus T*OS or TOSZ). If so, I'm happy to make a PR for this.

It seems that Plover has an entry of PH*PB for "mountain", which I think is good since it's easy to stroke and remember. However, it doesn't seem to gel with other current mountain-related briefs in dict.json like the following, that use the stroke of PHOUPB/TAEUPB, or some variation of it, for "mountain":

"PHOUPB/TAEUPB/SAO*EUD": "mountainside",
"PHOUPB/TAEUPB/SAOEUD": "mountainside",
"PHOUPB/TAEUPB/TKAOU": "Mountain Dew",
"PHOUPB/TAEUPB/TO*P": "mountaintop",
"PHOUPB/TAEUPBDZ": "mountainside",
"PHOUPB/TAEUPBS": "mountains",
"PHOUPB/TPHOUS": "mountainous",

So, my question is, is it worth adding the PH*PB as a brief for only the standalone word "mountain"? It doesn't seem to be compose-able, so you can't stroke, for example, "PH*PB/SAO*EUD": "mountainside" since there will be a space between "mountain" and "side", so that would be a potential strike against it. Any particular opinions for or against PH*PB?

In Plover release weekly-v4.0.0.dev8+66.g685bd33, there is no entry for the stroke KPHRAOUGS to mean "exclusion", yet it is included in briefs.json and top-10000-project-gutenberg-words.json.

Rather, the only single stroke entry for "exclusion" in Plover is SKHRAOUGS. Also, the two-stroke entry EBGS/KPHRAOUGS for "exclusion" is apparently considered valid in Plover, but that entry is currently in misstrokes.json. Furthermore, there is a stroke SKHRAO*UGS for "exclusion" in dict.json that does not seem to be in Plover.

So, my questions are:

• Should KPHRAOUGS be moved to bad-habits.json and the KPHRAOUGS entries in briefs.json and top-10000-project-gutenberg-words.json be replaced with SKHRAOUGS?
• Should EBGS/KPHRAOUGS be removed from of misstrokes.json and added (back?) into dict.json?
• Should SKHRAO*UGS be removed from dict.json and added to bad-habits.json?

In top-10000-project-gutenberg-words.json, the stroke used for the word "expansion" is:

It would seem to take this from the briefs.json dictionary:

The problem here is that there is no single-stroke entry for "expansion" in Plover release weekly-v4.0.0.dev8+66.g685bd33, only two-stroke entries:

expansion:
   EBGS/PAPBGS
   EBGS/TAPBGS
   EBGS/KPAPBGS

Given this scenario, what action is best to take?

• Remove "KPAPBGS": "expansion" from briefs.json (and maybe add it to bad-habits.json)?
• Change the top-10000-project-gutenberg-words.json entry for "expansion" to another stroke? If so, my vote would be for "EBGS/PAPBGS": "expansion"

In the current dict.json file, there are the following single-stroke entries for the word "concentration", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"SKRA*EUGS": "concentration",
"SKRAEUGS": "concentration",
"SKRAUGS": "concentration",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "concentration" used is:

Although Plover says it's a valid stroke, I am wondering whether perhaps SKRAUGS is a mis-stroke due to it not having an elongated "ā" sound (AEU) included in its stroke, which is what I would have expected for the word "concentration". So, I would propose:

• Removing "SKRAUGS": "concentration", from dict.json
• Adding "SKRAUGS": "concentration", to bad-habits.json
• Changing the stroke for "concentration" in top-10000-project-gutenberg-words.json from SKRAUGS to SKRAEUGS

There are currently entries in the Typey-Type dictionaries for "ext":

and "proc":

but neither EGBT nor PROBG exist as strokes in Plover release weekly-v4.0.0.dev8+66.g685bd33 (EGBT does not resolve to anything, while PROBG resolves to "probabling").

So, since the words "ext" and "proc" are in the top-10000-english-words.json dictionary, and hence are used in Typey-Type, did you want to replace the strokes for these words with their finger spellings, or perhaps replace them with other words...?

In the current dict.json file, there are the following strokes for the word "tension", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"TEPBGS": "tension",
"TEPBLGS": "tension",
"TEPGS": "tension",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "tension" used is:

Although Plover says it's a valid stroke, I am wondering whether perhaps TEPGS is a mis-stroke due to it not having the full PB stroke for "n" included in its stroke, which is what I would have expected for the word "tension". Therefore, I would propose:

• Removing "TEPGS": "tension", from dict.json
• Adding "TEPGS": "tension", to bad-habits.json
• Changing the stroke for "tension" in top-10000-project-gutenberg-words.json from TEPGS to TEPBGS

In the current dict.json file, there are the following strokes for the word "secondly", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"SEBG/TKHREU": "secondly",
"SEBGD/HREU": "secondly",
"SEBLGD": "secondly",
"SELGD": "secondly",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "secondly" used is:

Although Plover says it's a valid stroke, I am wondering whether perhaps SELGD is a mis-stroke due to it not having the BG-stroke-for-"k" included in its stroke, which is what at least I would have expected for the word "secondly".

Given that:

The two-stroke entries for "secondly" in dict.json use the full BG stroke for their "k" sound:

"SEBG/TKHREU": "secondly",
"SEBGD/HREU": "secondly",

I would propose:

• Removing "SELGD": "secondly", from dict.json
• Adding "SELGD": "secondly", to bad-habits.json
• Changing the stroke for "secondly" in top-10000-project-gutenberg-words.json from SELGD to SEBLGD

In the current dict.json file, there are the following strokes for the word "completely", all of which are valid in Plover release weekly-v4.0.0.dev8+66.g685bd33:

"KPHRAOELT": "completely",
"KPHRAOET/HREU": "completely",
"KPHRELT": "completely",
"KPWHRAOELT": "completely",
"TKPHRAOELT": "completely",

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "completely" used is:

Although Plover says it's a valid stroke, I feel that "KPHRAOELT": "completely" with the elongated "ē" sound (AOE) is a more accurate entry pronunciation-wise (and all the other entries use AOE), and so would like to propose:

• Removing "KPHRELT": "completely", from dict.json
• Adding "KPHRELT": "completely", to bad-habits.json
• Changing the stroke for "completely" in top-10000-project-gutenberg-words.json from KPHRELT to KPHRAOELT

In the top-10000-project-gutenberg-words.json dictionary, the stroke for "major" used is:

PHAEUPBLG is also another valid stroke for "major" in Plover, and I think this stroke, with the elongated "ā" sound, is more of a natural fit for the word "major" than the PHOEUPBLG stroke with the "oi" (OEU) sound.

So, I would like to propose changing the stroke used for "major" in top-10000-project-gutenberg-words.json from PHOEUPBLG to PHAEUPBLG. What do you think?