Dictionary Suggestions #400
Comments
Update dictionary with feedback from #400
|
I've removed a few thousand misstrokes I think from the main dictionary for myself where the commit history mostly shows why I felt the stroke was off: https://github.com/dimonster/plover-dictionaries/commits/master/dictionaries/dict.json |
Added:
```
"KPHR-": "a couple",
"KPHR-F": "a couple of",
"KH*EF": "chef",
"PHRU/TOBG/RAES/-S": "plutocracies",
"PHRU/TOE/KRAT/EUBG": "plutocratic",
"PHRU/TOE/KRAT": "plutocrat",
"PHRU/TOPB/PHEU": "plutonomy",
"OEL/TKPWARBGS": "oligarchs",
"OEL/TKPWARBG/EUBG": "oligarchic",
"OEL/TKPWARBG/EUBG/*AL": "oligarchical",
"TPHAOEFT": "naivety",
"TPHAOEF/TEU": "naivety",
"KWR*URS": "yourself",
"KWR*URS/-S": "yourselves",
"KWR*URSZ": "yourselves",
"HEUPLS": "himself",
"THEPLS": "themselves",
"SPHEUFD": "dismissed",
"TKPHEUFD": "dismissed",
"STKPHEUFD": "dismissed",
"TKUP": "duplicate",
"APB/STET/EUBG": "kinesthetic",
"APB/STHES/EUBG": "kinesthetic",
"APBS/THE/TEUBG": "kinesthetic",
"APBS/THET/EUBG": "kinesthetic",
"APB/ES/THET/EUBG": "kinesthetic",
"PWR-BT": "[",
```
Changed:
```
"PAL/TO": "{palato^}", → "PAL/TO": "{palato^}",
"KHEF": "chef", → "KHEF": "achieve",
"SKWR*UFT": "just", → "SKWR*UFT": "adjust",
"OPB/KO": "onco", → "AUPB/KO": "onco",
"OPB/KOE": "onco", → "AUPB/KOE": "onco",
"AOEFT": "East", → "AOEFT": "east",
"PWR*BGS": "{[}", → "PWR*BGS": "{^[^}",
"PWR-BG": "{[}", → "PWR-BG": "{^[^}",
"PWR-BGS": "{]}", → "PWR-BGS": "{^]^}",
```
Removed:
```
"TKPWHR-FPLTD": "glkjblkwoieuorui",
"HRAEU/OUT": "lay out",
"HRAEU/O*UT/SAOEUD": "lay outside",
"APB/ALG": "an additional",
```
…onary.
Added:
```
"SAOEM/-LS": "seamless",
"TKORBL": "adorable",
"A/TKOERBL": "adorable",
"TKOERBL": "adorable",
"TWUPBD": "on the one hand",
```
Changed:
```
"WEFT": "West", → "WEFT": "west",
"TP-BG": "{,}", → "TP-BG": "{!}",
```
Added: ``` "HOPBLS": "honestly", "HOPBS": "honest", "HOPBTS": "honesty", "RAOERL": "really", "TAOEFRP": "teacher", "KPAL": "capital", "SPRAED": "spread", "KAUPB/TKPWRAD/HRAEUGS/-S": "congratulations", "KAUPB/TKPWRAPBLG/HRAEUGS/-S": "congratulations", "KOPB/TKPWRAD/HRAEUGS/-S": "congratulations", "KOPB/TKPWRAPBLG/HRAEUGS/-S": "congratulations", "TKPWRAD/HRAEUGS/-S": "congratulations", "TKPWRAPBLG/HRAEUGS/-S": "congratulations", "KAUPB/TKPWRAD/HRAEUGS": "congratulations", "KAUPB/TKPWRAPBLG/HRAEUGS": "congratulations", "KOPB/TKPWRAD/HRAEUGS": "congratulations", "KOPB/TKPWRAPBLG/HRAEUGS": "congratulations", "TKPWRAD/HRAEUGS": "congratulations", "TKPWRAPBLG/HRAEUGS": "congratulations", "SEUFP/WAEUGS": "situation", "AEUFRD": "afraid", "SEUFRL": "silver", "SPWAOEUD": "beside", ``` Changed: ``` "MUFLS": "muscles", → "MUFLS": "muffled", ``` Removed: ``` "AT/TPHAT": "alternate", ```
Update dictionary with feedback from #400
…roject#400 (openstenoproject#582) Dictionary fixes and additions
|
I think the |
|
"culd" is not a word (at least not in modern English - apparently it's an obsolete form of "could"), so I propose removing |
|
|
|
I propose either removing EUPBD/KWRAB or changing it to be a misstroke for Indian instead of India. |
|
"Roentgen" came out instead of "rent again" haha |
+ A/KUFPL": "accustom",
+ "KARS/ER/RAL": "carceral",
+ "KARS/RAL": "carceral",
+ "STAURNT": "restaurant",
+ "TAURNT": "restaurant",
- "SKWRUS": "{^}{^us}",
+ "SKWRUS": "{^us}",
- "SRUFR": "Have you ever",
+ "SRUFR": "have you ever",
- "HRES/EPB" : "{lessen^}",
- "HOEUFLT": "healthy",
+ "HO*EULT": "healthy",
+ "SKED/AOUL": "schedule",
- "SKWRAURBGS/PAOE/KWRAPB": "piano",
+ "PAOE/KWRAPB": "piano",
+ "SKOPB": "scone",
+ "KAOEU/PWORB": "kibosh"
+ "PHO/KA": " mocha"
+ "PHOBG/KA": " mocha"
+ "PHOBG/KWRA": " mocha"
- "PHEFRPB/TKEUZ": "merchandis"
+ "PHEFRPB/TKEUZ": "merchandise"
- "TPHRAEUT/TO": "tomato", |
|
|
|
|
|
|
|
should be corrected to It's "anemone", not "amenome". |
|
Most of these I have no idea what they are supposed to do, so I just removed them for myself. Not sure what are these. Bad conversions? Probably bad conversions: Seems to be a bad conversion; should probably be No idea what this is: Probably bad conversions; should all have a |
|
This is a list of words for consideration which I could not find in Plover's dictionary. I added them to my own dictionaries (with outlines that felt right to me) while working through Platinum Steno's theory lessons. |
|
(Edit 8 months later: As slampisko says below, "pre- or" does make some sense. And "ordain" should probably be written as |
It makes some sense (e.g. Is that $5.39 pre- or post-tax?), but it doesn't come up that often and can be substituted by |
|
I've just found |
Made it to <openstenoproject#400 (comment)>
|
|
|
Very useful for beginners. Some of the other suggested commands might also be useful. (Alternatively, it could be good practice for learning how to add to the dictionary?) |
|
|
|
|
Although inversions should technically only happen between adjacent sounds, you can find this "rule" broken from time to time. |
Not just technically, but invariably, inversions should only happen between adjacent sounds. At least, according to Learn Plover. If there's a well established convention for this not being the case, then fair enough. Perhaps the docs could be updated to mention these exceptions? |
You can try emailing Zack about this—he replies pretty quickly. But I would argue that since
This only applies to phonetic write-outs (which Learn Plover! is primarily for). Briefs aren't restrained by theory rules and can be completely arbitrary sometimes. |
|
Ah right, I didn't realise they were briefs. Is there a way to tell what is a brief and what isn't? |
|
On Sun, Nov 27, 2022 at 1:54 AM Aerick ***@***.***> wrote:
Perhaps the docs could be updated to mention these exceptions?
You can try emailing Zack about this—he replies pretty quickly. But I
would argue that since SKWRERPBDZ is a brief, I wouldn't expect a
beginner to have to memorize an outline like this from the beginning. It's
more crucial to just stick to phonetic write-outs (like SKWREPB/TKER in
this case). And these are just exceptions, not rules (for example HRERPBD
is "learned" instead of "lender"). Including these might be more confusing.
Not just technically, but invariably, inversions should only happen
between adjacent sounds.
This only applies to phonetic write-outs (which Learn Plover! is primarily
for). Briefs aren't restrained by theory rules and can be completely
arbitrary sometimes.
It's true -- Learn Plover! is mostly concerned with "generic" theory, which
I think is very similar across a lot of different steno systems. It's
mostly the briefs that distinguish any particular theory from the others.
But I could be wrong.
As for updating the docs -- I'm sad to say that Learn Plover! is not
maintained at the moment. Ever since google migrated to the new version of
Google Sites, I haven't found a great way to adapt to the "web 2.0" look
and feel, especially since they don't allow the inverse text coloring that
I use for strokes.
My hope is that the whole site could be migrated away from Google Sites to
something more community-maintained, like in the github codebase itself.
I'd be happy to help with that if it's desired; though even then I would
probably let the community continue to maintain the pages collectively,
rather than taking an active role myself as 'maintainer'. I proposed
something like this awhile back, but there didn't seem to be much interest.
So the pages on Google Sites are currently simply languishing, going
gradually further and further out of date.
Gazareth said:
|
| Ah right, I didn't realise they were briefs. Is there a way to tell what
is a brief and what isn't?
|
If you mean, does the dictionary identify entries as briefs or nonbriefs, I
don't think so. But a brief is always an entry that violates the phonetic
theory. If you look through the dictionary, there are lots of words that
have tons of entries, and generally only one or two of those follow the
phonetic keystrokes. The rest are all technically "briefs", although you
should definitely not simply use a brief on faith. A lot of dictionary
entries are intended to correct for mis-strokes. I.e. they are mistakes. So
if you just see something that violates phonetic theory and start to use
it, you could be memorizing a mis-stroke instead of a proper brief. As I
understand it, briefs generally try to follow some sort of logical
structure, so that large groups of similar words will use the same little
gimmick in their briefs. It's a lot less usual for a brief to just be an
arbitrarily chosen keystroke. So, one way to identify which dictionary
entry is a brief and which are mis-strokes is to look for other entries for
other words, that use the same little gimmick. Likewise, mis-strokes can
give themselves away, for example they have the same number of strokes as
the phonetic version; or they way they violate the phonetic version is by
using a key that is right next to the key you would have used for the
phonetic version. But you need to be aware that briefs can also have
mis-stroke entries in the dictionary. So a mis-stroke could use fewer
strokes than the phonetic version yet still be a mis-stroke.
I hope some of that is useful.
Be well,
Zack
—
… Reply to this email directly, view it on GitHub
<#400 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANV2YTWNNY4TBMMFW45LPTWKKWNXANCNFSM4B5JFHPA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Zack Brown
|
and others
Report suggestions for changing the default dictionary in this thread
Just reply or edit posts to give suggestions, we'll remove them as they get fixed.
The text was updated successfully, but these errors were encountered: