Steno chord dictionary1/24/2024 ![]() However, for someone like me who likes using steno for typing tests, it's just not ideal. For court reporters and captioners, I suppose this isn't a huge problem as you're always hearing words and translating them to text. This is, of course, a good thing as you'll be writing shorter-but sometimes you just don't know which vowels are unstressed. This is just one example of an inconsistency within main.json.Īnother gripe I have with the above example is that all of these entries rely on the user having to drop unstressed vowels. I also need to mention that this isn't just a problem for "-ous" specifically. Many people use the dictionary lookup feature to learn Plover and these kinds of inconsistent entries make it really hard. There shouldn't be any priority between the two as that will just lead to unnecessary entries and confusion for learners. If the dictionary is going to have entries with US and OUS, both of them should be consistently used. But the dictionary's inconsistencies make such rules hard to set in stone. This is, of course, not a hard problem to fix just write about these hidden rules online and link to them in the Learning Resources page. You might notice that PHOPB/TPHOT/TPHUS is not defined even though it should work.Īlthough more experienced users of Plover and its dictionary may be able to tell you that main.json prefers OUS over US when a word is spelled with "-ous", this is not written anywhere in any resources. It's a good principle in theory One issue with just including as many translations as possible for a single word is that it confuses the learner if it's known that some entries might be "wrong" (i.e., misstrokes)., but it's just not executed well in main.json. That way you don't have to think about how you have to break up a word. Now of course, the whole point of main.json is that it will have all the different ways of breaking up a word into its syllables. ![]() ![]() Which of the above should you use? If you must know, any of the entries using US I'd consider as "wrong" in main.json and would advise against using. So what are some examples of inconsistencies within Plover's main default dictionary? Well, here are just a few that I find annoying: I'm also not a believer of keeping misleading entries in the Plover dictionary and leaving it to the learner to figure out which ones are incorrect. ![]() The goal of my rewrite is to provide rules that make writing out words less uncertain and hairy. ⊕ Even after you learn how to read raw steno.this is quite daunting. They may have followed Plover theory, but as I'll talk about later, the theory itself is still quite ambiguous in certain areas. Many of the entries in main.json are just simply what made sense to Mirabai at the time and did not follow carefully designed systematic rules. That said, tailoring our dictionaries to our own writing style limits its usability to fewer people. We tailor our dictionaries to match how we think language should be compressed and what rules make sense to us. That is why stenographers don't learn (or can't learn) one "correct" dictionary/theory. The way we perceive language and phonetics (such as accent and dialect differences Unfortunately, my dictionary rewrite still depends on having a standard American accent, though there is one person working on an English theory that is not dependent on accents.) influence what rules work best for us and how we construct our own briefs. But of course everyone writes differently. Main.json is Mirabai Knight's personal dictionary and it obviously works really well for her. In this article I want to talk more about my motivations and why I decided to take on the momentous of manually adding over 60,000 entries to a steno dictionary. You can find all the new rules and differences my dictionary has with main.json over at my GitHub repository. The inconsistencies make it hard for beginners and learners, and force users to have to add entries to their dictionary which, many people including me, deem unnecessary. There's even a thread in the Plover Discord all about rewriting the dictionary with automation. This isn't just a complaint that I have with it it's pretty well known in the Plover community that main.json is lacking in these areas. Why? Well there are several reasons, but in short, I'm not a huge fan of the inconsistencies and lack of rules that come with main.json. I wanted one that would be able to replace Plover's very own main.json that came by default. Why I'm building my own dictionary Why I'm building my own dictionaryĪ few months ago, I decided to build my very own steno dictionary for the English language from scratch.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |