Tuesday, May 28, 2013

Plover Documentation Project

Recently I was contacted by a technical writer who was interested in learning steno. He wanted to use it not only to be more productive and ergonomic in his day job, but for his personal creative writing projects as well. I know that the Steno 101 series is full of holes (no practice material, overly dense explanations) and is pretty inaccessible to the typical steno newbie. He proposed an exchange: I would tutor him in steno, and he would write up those sessions in the form of clear, comprehensible documentation. Since this whole pedagogy thing has turned out to be way harder than it initially looked, I leaped at the chance. Yesterday we met, and it was fantastic. We talked steno over dinner, then went to his apartment and stepped through some beginner stuff. First, we looked at the Steno Alphabet Posters. He told me that, logically enough, he'd assumed that if he pressed the keys corresponding to each letter of the chart, Plover would output those letters and he'd be able to use them to spell words. I realized just how confusing the chart's layout was without explanation, and had to explain that if you want to spell words out letter by letter, you have to ignore all the keys on the right hand side of the chart, and only use the chords on the left side, plus you had to add either asterisk or asterisk plus right hand P if you wanted to spell out letters. Otherwise the chart was intended to demonstrate where the letter sounds appear in steno chords, not on their own. I'm not sure I'd ever articulated all that before, in so many words, and it seems to have confused a lot of newbies. So we were already synthesizing some good tidbits of wisdom to put down. I asked him whether he preferred the chart in "alphabetical" or "pedagogical" order, but he said he wasn't yet experienced enough to decide. Then we went on to writing:

"The quick brown fox jumps over the lazy dog."

which, in pseudosteno, is:

KPA -T KWIK BROUN FOX JU*MS OEFR -T LAIS/YI DOG FPLT

and, in actual steno, is:

KPA -T KWEUBG PWROUPB TPOBGS SKWR*UPLS OEFR -T HRAEUS/KWREU TKOG FPLT

Everything was phonetic, except:

* The KPA stroke to capitalize the first word of the sentence.
* The "mp" sound, represented by "*m".
* "Over" sounding more like "oefr", though that's really very close to phonetic.
* The "-y" suffix, represented by "yi".
* The period, represented by FPLT.

But other than that, not a bad beginning sentence, and my new friend was blown away with steno's ability to write the whole thing, 44 letters long, in only 12 strokes. Then we went on to other topics, such as the fine art of "syllabification", whether learning "steno order" (STKPWHRAO*EUFRPBLGTSDZ) was a necessary part of mastering the keyboard layout, and whether inversion should only be used if it allows you to save yourself a stroke. All good stuff, but he'll write it up much more cogently than I can. The upshot of all this is that we'll be meeting weekly from now on, and I think we'll be able to drum up a lot of useful practice material, which is something that the Plover community has been desperately needing. We might even get to the point where we start wireframing out the Hover Plover tutorials. I'm extremely lucky to have found someone who enjoys geeking out about steno as much as I do, and who has the skill to turn my random blibs and blobs of knowledge into a coherent plan for self-instruction. So stay tuned! Lots more good stuff to come.

12 comments:

Snowy Wilderness said...

This is SUPER exciting! I can't wait to see what you two come up with!

Steven Bhardwaj said...

I second above motion by Snowy Wilderness. Not-able-to-waiting here.

Jonathon Ashworth said...

This is fantastic!

I'm a steno newbie, trying it for something new after topping out my speed with Dvorak, and I'm really struggling with some things.

The biggest example I can think of now is a race I just did on Typeracer with the word:

carryin'

in it.

I can't figure out how to put an apostrophe like that on the end of a word, I don't think it's documented anywhere (or I missed it, which is more likely :P)

Also is there any way to stroke out a word then fingerspell the ending to it. I ended up just fingerspelling "carryin", but it would be much faster to type KA*R then fingerspell the "in", I tried that, but couldn't figure out how to glue the two together, since fingerspelling something starts a new word. I'm sure I've read how to do this somewhere, but I can't find it again.

Mirabai Knight said...

Hi, Jonathon! Sorry about the frustration. Steno definitely has a learning curve, but we're slowly trying to rectify that by producing better and more coherent information for steno newbies.

My best advice for carryin' would be to write carrying (KAERPBG), then Backspace (PW-RP) the g, and then do AE for the '. It's three strokes, but it's still better than doing it qwerty style, which would be eight strokes. Hope that helps!

Mirabai Knight said...

Oh, and if you want to glue two words together, use TK-LS in between the two halves.

Mirabai Knight said...

Sorry, that's PW-FP for Backspace, not PW-RP.

Anonymous said...

I was looking around and apparently you can use Inform 7 to write text adventures with plain text! Neat, huh? Just one more thing to do.

Mirabai Knight said...

Sweet! Good to know! Saving the link here for future references. Writing a text adventure sounds like a TON of work, but is probably really satisfying.

http://inform7.com/

David Friedman said...

Re: Jonathon Ashworth's question

Looks like in Plover as of version 3.0.0 PW-FP got overwritten to be "before" but that PW*FP is still backspace.

PW*FP is listed in commands.json, while PW-FP is listed in commands.json as being backspace, but also in main.json mapping to "before". PW-F is also mapping to "before".

Looks like the version I have on here now was downloaded May 9th, 2016 but I checked the GitHub repository and main.json and commands.json haven't been modified since then.

Mirabai Knight said...

Thanks for bringing this to our attention. I definitely think PW-FP should be backspace and not before. We should fix that.

David Friedman said...

oh okay, glad that that was helpful.

I added that to the Dictionary errors issue on GitHub.

https://github.com/openstenoproject/plover/issues/400

Mirabai Knight said...

You're awesome. Thank you!!