Quantcast
Channel: The Plover Blog
Viewing all 512 articles
Browse latest View live

Captioning With Plover and Vim

$
0
0
As promised, here's my video of using Plover to enter and edit text in Vim!



And in case you're interested, here are the steno definitions of the commands I use in the video:

"STPAO*EUL": "{#Escape}:w c:/proj/.txt{#Left}{#Left}{#Left}{#Left}{^}",

"STPHA*EUF": "{#Escape}:silent w{#Return}:{#Return}{#Control_L(End)A}",

"SPO*EL": "{#Escape}:set nospell{#Return}:{#Escape}{#Control_L(End)}A",

""SKHR*EBGS": "{#Escape}/zxzxz{#Return}:{#Escape}A",

"PHOEUFP": "{`^}

"SPWAO*UT": "{#Escape}:%s/{^}",

"KW*RPB": "{#Escape}{>}bvwy:split c:\\proj\\plovernotes.txt{#Return}o{#Escape}jp:silent w{#Return}:silent q{#Return}:{#Escape}{#Control_L(End)}A",

"SR-RS": "{#Escape}{#Control_L(End)}A",

"TKHREPBD": "^vG$xo",

And bonus definition which I use in the video to get rid of an extra space but don't mention specifically:

"TW*EUT": "{#Escape}:set textwidth=46{#Return}ggvG$gq:%s/  / /g{#Return}:%s/ \\n/{#Control_L(Q)}{#Control_L(M)}{^}/{#Return}:%s/\\n /{#Control_L(Q)}{#Control_L(M)}{^}/{#Return}:%s/\\n\\n\\n/{#Control_L(Q)}{#Control_L(M)}{#Control_L(Q)}{#Control_L(M)}/{#Return}:silent w{#Return}{#Escape}/zxzxz{#Return}:{#Escape}{#Control_L(End)}A",


Two Quick Links

Stenomatic 9000

The Cumulative Effect of Of, The, And, and To

$
0
0
A brief but notable gem from ellispratt on the Aviary:
Peter Norvig has some interesting statistics on word frequency in the English language http://norvig.com/mayzner.html Four words - the of and to - account for 16.94% of the words we write. If you include the need to press the space bar, these four common words require an average 3.5 key presses on a QWERTY keyboard. Steno requires one. In the field I work in, technical communication, a Technical Writer spends 50% of their time writing (the rest on researching, planning etc). Adjusting for the fact that these four common words are half the length of an average word in English, that means they spend an average of 19 minutes every day (1 hr 35 mins in a 37.5 hr week) typing those four words on a QWERTY keyboard! With Steno, I estimate it would take just under 5 and a half minutes/day (27 mins a week).

Back From Vacation!

$
0
0
The new semester has started, and I'm finally settling into a groove. I'm still working on a big post about where I see the Open Steno movement going over the next few years, but for now I just want to post a few brief updates.

First off, looks like the Sharkoon Tactix keyboard I posted about recentlyapparently doesn't have full n-key rollover after all, despite what it claims. So the price is nice, but it's not going to work for Plover. Bummer.

Secondly, The Aviary has really been hopping lately. It's been quiet for years, but it seems like it's actually achieved something of a critical mass in recent months, with some great conversations happening between various users. Unlike the Google Group, which is focused more on tech support and discussion about the future of Plover, the Aviary is more of a place to talk about your day-to-day steno learning process. I check it every day, so you can also ask questions about steno theory, and when I answer them, they'll be up for the reference of other Aviary users. If you haven't been there recently and you want to talk about the ups and downs of learning steno, go check it out!

And finally, I bought some elastic, Velcro, and fabric adhesive at a craft store the other day. I've been carrying my Stenoboard around in my backpack for months, but I don't often use it, because I can't seem to find a typing position that's both comfortable and secure. I'm so used to the tripod-based system I use with my Infinity Ergonomic that resting the two halves of the Stenoboard on a table just feels too flat, and I haven't figured out any other way to replicate my preferred double-handed tilt. So my eventual goal with all these supplies is to make a more durable and adjustable version of the thigh-mounted setup I depicted in my Mobile and Wearable article. The Stenoboard is much smaller and more lightweight than the Gemini2 in that picture, so I'm hoping it'll be a lot less unwieldy and a lot more comfortable. I'm not generally so good with arts and crafts, but if I can manage to make a stable, secure attachment for my Stenoboard that allows me to quickly set up and start writing sans tripod, I'll be really happy. Stay tuned to see if I can manage it!

Stenosaurus Update!

Stenowiki and Bob's DIY Machine

$
0
0
The redoubtable ezyang (of Stenomatic 9000 fame) has created StenoWiki, a collaborative database intended to categorize and explain definitions in the default Plover dictionary! When a beginner first starts learning steno, it can be tricky to develop the skill to tell a misstroke from a brief or a semi-phonetic stroke from a completely phonetic stroke. This wiki helps to bridge that gap!

Also, Bob from the Google Group has just converted an old manual steno machine into a Plover-compatible device!

He writes:

"I managed to complete the stenotype to digital.

I was asked to post some pictures of the process. This is the 1st. This is the one I will start learning with.

My total conversion cost was about $30.

If I add the cost of the Stenotype I have a fully working setup for less than $75.00.

I found the stenotype on ebay delivered for $28.00. I'll be ordering another to incorporate updates I want to make to it. With the cost being this low it won't be expensive at all to have a backup system."

Check out the pictures! Pretty dang impressive, I have to say.

Pre-Stenosaurus Crowd Supply Campaign!

$
0
0
Many exciting things to report!



First off, Josh Lifton, Plover's first developer and inventor of the forthcoming Stenosaurus, has launched a crowdfunding campaign to offload some of the extra custom keys he commissioned from Matias as a way of raising funds for the very nearly imminent Stenosaurus campaign launch. It's already almost halfway funded, but if you're a hardware hacker with a need for quiet, lightweight, feather-touch keys with a dead simple mounting system, go pick up a bag of 150 for $50. Heck of a deal!

Also, the amazing Ed (aka ezyang of Stenomatic fame) has put a Starter Guide up on the Wiki to help ease new steno learners into the fray. Ed's got a lovely friendly conversational style and extremely solid advice. If you're intimidated about where and how to get started, definitely go check it out.

Speaking of new steno learners, Lars has been keeping an online diary of his learning process. He's only been doing it for a week, but he's already up to almost 60 WPM on single-stroke words! Pretty dang impressive.

Finally: Ellis, a technical author and relatively new convert to Plover who's already been able to double his typing speed, recently wrote a blog post on his company's website extolling the advantages of steno for members of his profession. In his post, Ellis included a link to an Ignite Talk Josh gave to the Technology Association of Oregon some months back, which I'd been dragging my heels on captioning for no good reason whatsoever. But thanks to Ellis's post, I finally just sat down and did it. The captioned version is embedded below. It's fantastic five-minute précis of just how powerful and useful open source steno can be. Check it out!




Another Awesome DIY Plover Board

$
0
0


Check out this beautiful DIY Plover Board built by Timothy Aveni for less than $100!

Seriously impressive.

Speaking of DIY keyboard projects, The Matias Keyboard Switch Crowd Supply campaign is 176% funded and already shipping out keysets. Josh says he's hoping the Stenosaurus Crowd Supply campaign will go live in the next two or three months, which is tremendously exciting.

On a more discouraging note, our previous go-to low-cost n-key rollover keyboard, the Sidewinder X4, is now well and truly out of production, so prices for leftover stock are climbing inexorably upwards. This is really a shame. At its best, it cost around $45, but now you'll have to pay around $70 for a used one and $150 or more for a new one.

There's currently a Massdrop for a $50 Noppoo Lolita Spyder 87, but that won't last forever, and retail for the Spyder is around $80. I really hope that a new low-cost gaming keyboard with true nkro (not fake nkro like the disappointing $20 Sharkoon) comes around again soon. There's a surprisingly big difference between $50 and $100 when you're talking experimental entry-level steno. I'll always be grateful to Microsoft for releasing the Sidewinder right when I started the Plover Project back in 2010, and I know that all manufacturing efforts have a limited lifespan, but I sure hope something else comes up to take its place.

Monday Miscellany

$
0
0
Just two quick items:

* Emanuele has started a Stenoboard blog. There's only a welcome post on it so far, but if you're interested in the progress of the Stenoboard, you might want to add it to your RSS reader of choice.

* Also, it's not strictly Plover-related, but Drew from the Plover Google Group told me about a Vim plugin that's turned out to be life-changing: Vim-G. As Drew explained:

"It provides a :Google command that lets you run your query direct from Vim. Additionally, if you select a word then run the :Google command, it will search for the selected word."

So I've been able to map my TKPWHREFRPB command to {#Escape}:Google{#Return}, which will open a Chrome window and search for the word under my cursor. This is so great for looking up words while editing CART transcripts! Previously I'd tried to do it by using Launchy, but because there's currently no way to make definitions with predetermined "wait x milliseconds" commands, the processes would get out of sync and wouldn't execute properly. This solves that problem completely. It's still probably worth building a "wait" command into Plover at some point, but now that I have this Vim-G solution, that feature is not as urgent for me as it once was.

Plover-Inspired Geocache Puzzle!

$
0
0


Check out the amazing epistolary tale of Doris Plover, Court Stenographer circa 1935!

I was contacted by someone trying to solve it (it's since been solved, but you can try it yourself for practice; translating the steno is only the first step toward finding the correct location of the cache.) The pedant in me has to admit that the stenography is not 100% accurate for the time period (You never need to write P/KPA* for a period; just FPLT will do, both for Plover and for non-realtime stenographers. Proper names don't need to be manually capitalized either. Also, they probably wouldn't have used long vowels, an asterisk-based fingerspelling alphabet, or S-P to work around a word boundary error; all of that stuff only came in when realtime was introduced in the 1980s.)

But even so, how mindbendingly awesome is this?!? I was absolutely tickled pink to find that it existed. Many years ago I made up a brief steno puzzle of my own for a friend who didn't know steno himself but who was interested in cryptography and wanted to see if he could figure it out without any prior knowledge. It makes me so happy to see that someone I don't even know had the same idea.

Even cooler is that after I helped the guy who was working on solving the puzzle, he made a $100 donation to The Open Steno Project! What a mensch! Money aside, learning that this thing existed seriously made my whole week. Thanks, Mysterious Puzzlemaker, whoever you are!

Odds and Ends

$
0
0
A few brief Plover tidbits for you on a lovely warm Monday afternoon:
  • On the Open Steno Blog, there's a wonderful essay by Paulo Paniago about his experience with adapting Plover to make it compatible with Portuguese and then essentially building a Portuguese dictionary from scratch! He now uses steno for all his typing, which he says is faster and more comfortable than qwerty. Great stuff.
  • On the Plover Google Group, user grytiffin posted some seriously cool photos of his tripod-mounted Ergodox machine. That looks like a Neutrino Group (Gemini/Revolution/Infinity) chassis holding the two halves of the Ergodox in place. He writes: "I traced, cut and attached 2 pieces of pine to the tripod, and rested the keyboard on the pine. The metal brackets are temporary until I can think of something else more elegant.  Next step, upload a keyboard layout to assign the vowels to the big orange keys." Just gorgeous.
  • Meanwhile, on The Aviary, user skwropb posted a fingerspelling dictionary that force-caps uppercase letters and force-uncaps lowercase letters, which is especially useful for Vim users like me. I've been using it for a while now, and I love it. No more unexpected actions after writing punctuation and then going into command mode!
  • Speaking of useful dictionary hacks, I've recently discovered a way to compensate for Plover's imperfect orthography for medical suffixes.

    {^}{^ase}
    {^}{^uria}
    {^}{^emic}
    {^}{^emia}
    {^}{^oma}
    {^}{^us}

    When adding "emia" (defined as {^emia}) onto "hemoglobin", for instance, I would get "hemoglobinnemia", with the double n. Adding that extra {^} before the suffix circumvents Plover's orthography module and gives me the correct translation, "hemoglobinemia", without the extra "n". I'm adding these new suffixes whenever they come up by basically doing my "suffix define" stroke -- {^}\{^\}{#Left}{^} -- once, moving the cursor over to the right, and then doing it once more before writing the actual suffix. Comes in really handy when you're doing a lot of medical captioning, like I am.
  • Finally, I was lucky enough to get the chance to speak about steno and Plover at the Google Development Group's Women Techmakers Event last month, and I also wound up captioning most of the talks using Plover with Text-On-Top. You probably won't be able to glean much of what I talked about from my slides, since they're mostly just pictures, and unfortunately the event wasn't recorded, but I thought I'd post some pictures from it, just 'cause it was such a cool experience. There were about 100 people there, and I'd set my steno machine to send simultaneous Bluetooth to my Lenovo Helix running Text-On-Top plus my HP Stream7 running Plover with Vim. I also hooked up my StenoBoard to my Surface Pro so that people could come by during breaks and play on the machine for themselves. It was really fun, and I think I drummed up a fair amount of interest in Plover along the way!

  • And here's a 7-second video of me captioning the speakers as a group of us stood up in front of the audience to answer questions. Don't worry; there was another screen on the other side of the podium that was also displaying the captions, so we weren't blocking them out completely.

Open Steno App Wins Second Prize at Connect Ability Hackathon!

$
0
0


Last weekend, I attended the AT&T Connect Ability Hackathon at the NYU Ability Lab, a competition to create accessible technology with and for people with disabilities over the course of two short days. When I signed up, I was a bit worried that there would be nothing for me to do, since I don't know how to code, but early on Saturday morning I had the great good fortune of running into Jacob Mortensen, a freelance Android developer, and Rocio Alonso, an industrial designer for The Adaptive Design Association. My friend and colleague Stan Sakai was also there captioning the event, and between plenary sessions he was awesome enough to sit at our table and give us a hand with the work. The challenge was built around four exemplars, people who used various types of accessible technology and who had specific ideas of how it might be improved. One of these exemplars was Paul Kotler, an autistic college student who uses an augmentative and alternative communication device to speak via text-to-speech synthesis. Ever since 2010, I've been interested in the possibilities of using steno to improve the speed and efficiency of AAC. I knew that a stenographic solution might not work for Paul due to difficulties with motor planning, but his video spurred me in the direction of wanting to work on a realtime stenographic text-to-speech solution for the Hackathon.

We initially started with Brent Nesbitt's StenoKeyboard app, an Android-based open source clone of Plover, because we figured that a phone, with its integrated speaker and small display footprint, would offer us the easiest and most portable solution. We also selected StenoBoard for our hardware, because it's currently the smallest, cheapest, and most readily available steno system on the market. It's a bit too bulky to be perfectly wearable, but it beat out every other option that could be rigged up over the course of a single weekend.

For a thorough explanation of our design process, please check out our ChallengePost Page. We called our project (modified StenoKeyboard app + wearable StenoBoard mount) "StenoSpeak for Android". We worked right up to the submission deadline, and our final system wasn't without its bugs and foibles, but apparently it had enough potential to earn us second prize out of 15 teams competing in the Hackathon! Many, many thanks to Jacob, Rocio, and Stan for working so hard on this. It was a wonderful collaborative experience. Also huge thanks to Brent for StenoKeyboard and Emanuele for StenoBoard, without whom we would have been totally dead in the water.

What's next? We'll see. There are definitely some plans in the works, but our next big objective is to find an AAC user who might be interested in learning steno to help us with future iterations of the project. People with disabilities tend to be some of the earliest adopters and most proficient power users of accessible technology, so I'm hoping to find someone who can join our team as a full and active member while we work on developing this technology into a completely workable and replicable open source product. If you or anyone you know uses AAC to communicate, has full use of their hands, and is willing to spend a few months learning steno with our online textbooks, tutorials, and drilling tools, please get in touch!

Congrats to all of the Hackathon competitors, especially the first prize winner, Cameron Cundiff, with his brilliantalt_text_bot, and the third prize winner, the Tranquil Tracker team, with their seriously cool anxiety-tracking biometric device and app. And, of course, thanks to AT&T and the NYU Ability Lab for putting together this amazing competition!

Check out some photos from our whirlwind hacking weekend:


Rocio's wearable prototype sketches.


Stan modeling our ideal (though non-functional) wearable steno design.


The final (functional) wearable StenoBoard design.


The exultant StenoSpeak Team!

Three Rad Things

$
0
0
First, Lars (of Steno Diary fame) has updated Erika's PloverLearn modules to include analytics, plus drills for common briefs! Check 'em out at HaxePloverLearn.

Second, Charles has produced another homemade steno keyboard that's even snappier-looking than the last one:

.

He also includes an illustrated assembly walkthrough with a bill of materials, which comes out to about $120 in total. Pretty dang slick!

And finally, Stan Sakai, the ever-glorious Plover Poster Boy, has produced a brilliant little three-minute captioned whiteboard video explaining the rudiments of steno:



I'm in awe not just of his artistic skills (he actually drew the Plover bird!!!), but of his power to break down complex concepts into simple examples that nearly anyone can grasp. Seriously a tour de force.

Roslyn's Stenoboard Videos

$
0
0
I haven't gotten a chance to watch both of these all the way through, but I thought I should post them so that people who want more information on the StenoBoard can get a glimpse of what the assembly process actually involves. This one is uncaptioned, but it's mostly about the visuals, so the audio can be safely ignored:



And this one, with some ideas of how to make the StenoBoard more like a traditional lever-based machine, actually is captioned:



Roslyn described herself recently in the Plover Google Group this way:
I worked through all the LearnPlover modules in a few months last year on an nkro keyboard before deciding that I really did want to do this as a career. I probably spent about 10-15 hours a week, just fitting it in where I could (I had my three year old home with me most of the time, so it was a bit sporadic). Last October, I enrolled in Australia's only Court Reporting school (distance ed) and had to start again (using the manual machine they lent me) because they teach a different steno theory. I am about halfway through theory now - I do about 15-20 hours a week and we learn to write at 60wpm (from tape recorded drills). The main reason I didn't just continue self-teaching is because of the difficulty in getting a 'real' machine here in Australia. We have a very small industry compared to the US. I have recently bought a Stenoboard and I'm using that in conjunction with StenoTutor - it's really speeding up my progress because it lets me focus specifically on the words I'm writing slowest - I highly recommend it :-). At the rate I'm going, I'm hoping to be through theory and onto speedbuilding in another three months (although life still sometimes does get in the way!)
I think it's really cool that not only did Plover help her decide on steno as a professional career, but that it's inspired her to make videos that she can share with the wider open steno community. Very gratifying and much appreciated!

For-Profit Steno School Under Scrutiny

$
0
0
So it looks like the New York City Department of Consumer Affairs is investigating my old Steno School. Hm.

Honestly, I doubt it's any better or worse than most for-profit steno schools. I had a pretty good experience there, all told. The teachers were all actual stenographers, they were all pretty nice (even if the dictation they read us was as dry as lunar cheesedust), and nothing I learned there was actively wrong; it just wasn't particularly relevant to my chosen career. Possibly I would have gotten more out of it if I had wanted to be an actual court reporter, but virtually everything I needed to know about captioning for deaf and hard of hearing clients I had to teach myself. The main benefit NYCI gave me was in the speed testing process, a weekly metric they administered to tell me how quickly I was advancing, plus a financial sting in the form of trimesterly tuition payments, which motivated me to practice more and graduate faster. When you look at it that way, it's not unlike Beeminder, my favorite anti-akrasia device. I was lucky enough to get grants from the State of New York for my first year there, and paid for the other six months with a combination of cash and loans. I also had a job at the time (offline transcriptionist for a TV captioning company) that allowed me to pay rent and go to school while practicing steno 40 hours a week on the clock. I paid off the last of my steno school loans, along with the much more substantial loans from my undergrad degree, in January 2015. Steno has been a seriously good deal for me financially, and I'm not sure that I would have been as motivated to work as hard as I did if I hadn't paid any money at all and had no objective way to measure my progress. If you advance through speeds quickly, like I did, steno school can be a tedious but relatively painless avenue to a profitable, pleasurable, and endlessly challenging career. I'm a bit resentful that they made me go through six months of padded-out and puffed-up theory classes before they let us start taking speed tests, but otherwise I have no regrets.

I was one of the lucky ones. The problem is this: If you don't advance through speed tests quickly, these schools can keep you in limbo for years and finally graduate you in cataclysmic amounts of debt, or even worse -- which is what happens to the overwhelming majority of students, estimated at 85% or more by most accounts -- it can sell you a machine and software for thousands of dollars, squeeze tuition from you until you're the proverbial bloodless stone, then kick you out with absolutely nothing lucrative to show for it. This is bad. But it's certainly not just found at NYCI. Virtually every steno school operates on this model.

The fact is that back in the day, if you washed out from court reporting school, you at least had some shorthand skills you could use to take dictation as a secretary. The School for Stenotype Exclusively, later Stenotype Academy, and much later The New York Career Institute, was founded on this model. It didn't have any admissions requirements, and its tuition was relatively modest. Those that couldn't hack it had their mid-range clerical skills to fall back on, and those that could went on to work in courtrooms and deposition rooms. I doubt that they were graduating any more students then, proportionately speaking, than they are now, but the stakes for failure now are so much higher. You can easily lose tens of thousands of dollars while churning away for a 225 WPM speed certificate that might never be yours -- whether because you don't have the baseline literacy skills to produce a properly spelled and punctuated transcript, because your motor reflexes aren't fast enough, because your fingers aren't coordinated enough, because you didn't have time to practice, or any of a dozen other reasons. And if you don't get that certificate, there are no alternative careers waiting for you. People don't dictate to secretaries anymore. Bosses do their own typing, so typing skills on their own just don't pay the bills like they used to.

Steno schools that operated with nothing but the public good in mind would try to weed out the obvious never-happens and keep only the best possible prospects -- piano virtuosos, video game whiz kids, qwerty champs, and grammar mavens -- to train up into stenographers. But the National Court Reporters Association tried something like that a few years ago. They hand-picked 15 students, all with bachelor's degrees, who went through a rigorous admissions process and then submitted to constant supervision of their learning and practicing time. After two years, one student had achieved 225 words per minute, two were around 180, and the rest had given up.

My hypothesis is this: It's almost impossible to predict who's going to have what it takes to become a professional. Some mysterious combination of factors separated the hotshot professional qwerty transcriptionist with a Master's degree in literature -- who washed out of my steno school class around 140 WPM after two years of trying -- from me, who didn't have nearly the qualifications he did, but who got my 225 in 18 months. There are people who have gotten it in 11 months. Some have gotten it in 9. What do they have that the other students don't? No one has been able to figure that out. But that's why I think that professional certification shouldn't be the one and only goal in the steno world. If most people who learn steno only reach 140 WPM or 160 WPM and can't get a job as professional stenographers, does that mean the whole endeavor was wasted? Well, if they're out $20,000 and several years of full-time slogging? Yeah. That seems like they made a pretty bad decision. But if they're out $100 and a few months of practicing or playing a video game for fun whenever they have a spare moment? 140 WPM ain't chopped liver. If their day job consists of typing, they've just upgraded their qwerty keyboard for a vastly more efficient and ergonomic model.

This is why The Open Steno Project is so important to me. Right now the good name of steno is being spoiled by the exploitative for-profit steno school system. Far more steno students are losing money than making money, and no matter how you look at it, that's not right. That's not how a trade school should work. It might well be impossible to increase the success rate. If lots of people want to study steno, only a tiny fraction will ever become professionals, and there's no way of predicting which ones will succeed, the only ethical solution is to lower the stakes. Allow anyone to play around with steno on their own time, requiring only minimal financial investment. Those that have a knack and a passion for it can undergo more rigorous training and push themselves over the top, where the money is. Maybe that would involve a paid professional training program, but if so the admission requirement should be 150 WPM, at a baseline. The rest can do it for its own sake, for fun or to aid in other text-heavy pursuits. But even if they decide it's not for them, they'll only be out $100 plus whatever time they chose to put into it. They won't be miserably indebted and forcing themselves to work at something they hate and will never be good at. Debt and desperation will not keep my profession alive, and it will not keep my beloved stenographic technology alive. With its secretarial fallback base long since hollowed out, the for-profit trade school model is in the process of collapsing, and it's bringing thousands of financially captive students along with it. If steno is going to survive, it needs to be open and it needs to be free.

Keyboardio Kickstarter is Live

$
0
0

Back in August, a Plover fan asked the Keyboardio Twitter account if their keyboard would have true N-key rollover. They said they were working on it, and asked us how many keys of rollover we needed. I told them 16 or more would probably do the trick.

According to their Kickstarter page, they have succeeded:

"True N-key rollover (NKRO)

For a variety of reasons, many USB keyboards limit you to pressing 6 keys (plus modifiers) at once. Most of us would never notice this limitation, but an intrepid few really, really need to be able to hit more than six keys at once."

I'm not sure if that was a specific reference to the Plover community, but regardless, the thought is very much appreciated.

The column-based layout and tripod compatibility are certainly ideal for steno. I'm not sure the big ridges between the thumb keys will make for the most comfortable vowel writing, but they don't look sharp enough to be a dealbreaker.

At $300 per keyboard, it's certainly on the pricier side for a Plover-compatible keyboard that's not explicitly intended for steno, but if you anticipate a lot of mixed use, don't want to keep both qwerty and steno keyboards at the ready, and don't want to build your own Ergodox, the Keyboardio Model 1 is certainly an attractive specimen. The Kickstarter ends in 29 days, so you've got about a month to decide!

Beautiful Plover Skin for Rainmeter

$
0
0
Shayne from the Google Group writes:
I've created a little (Windows-only) desktop widget to show Plover's status (running/stopped) in a more aesthetically pleasing way than keeping the window up all the time to watch the big "P". After a few months of working out kinks, I think it's working well, and wanted to share it with you all:



It's a Rainmeter skin with three variants (left to right: bubble, icon, letter), with an AutoHotKey script included that needs to be running to alert Rainmeter.

How it works: the AHK script registers with the Windows shell to get messages whenever windows redraw; any time the Plover window does this, the script checks the window title ("running" or "stopped") and, if it's changed, sends a message to Rainmeter to refresh the skin, changing the colors.

Note that it requires both Rainmeter (http://rainmeter.net/) and AutoHotKeyAutoHotKey (http://ahkscript.org/) to run.

Available for download: http://monochromatope.deviantart.com/art/PloverStatusIndicator-1-01-541857076
Source available, too: https://github.com/shayneholmes/PloverStatusIndicator

How to install it: Download and install the .rmskin file, then run the .ahk file in the installed folder (and put a link in your startup folder so it runs on boot).

It is especially nice if you have a second monitor. Hope some of you find something useful in it.
Isn't it gorgeous? If you run Windows and you want something beyond the blocky and admittedly uninspiring Plover "P" box, go give it a try!

Open Steno Featured on Hackaday

$
0
0


Hackaday: Stenography (Yes, With Arduinos)

Kevin emailed me a few days ago with his awesome USB hack for Stentura 200 (which he says would almost certainly work for Stentura 400s as well), and I was just about to blog about it when I got tipped off to this article on Hackaday mentioning both Kevin's hack and a great write-up on the principles of Open Steno in general. Some of the comments are a bit wearying (to reply in brief: steno is not obsolete; courtroom reporters have not been replaced by speech recognition but by lower-paid qwerty typists; Siri is not going to be able to handle subpar audio, technical syntax and markup, or non-standard accents any time soon if ever), but the article itself is top notch! Highly recommended.

Also, Josh and I are going to be manning the Open Steno Project table at the 2015 National Court Reporters Association Convention here in NYC at the end of the month. I printed up a brochure for it:



And we're hoping to have a functional prototype of the Stenosaurus to show off while we're there. Fingers crossed! I'm also going to be using Plover to compete in the National Realtime Competition, but don't expect too much from me; I have a habit of choking during speed tests, so it's entirely possible I'll crash and burn in the first 30 seconds.

Lastly, if you haven't read Lars's Steno Diary in a while, it's really heating up! After just four months of studying/practicing for 20 minutes a day, he's able to write just about anything he can think of in steno, and he's currently working on putting together a robust dictionary for the purposes of writing, editing, and navigating code. Pretty dang badass.

Success Stories from Steno Autodidacts

$
0
0
Back when I started Plover in 2010, I had the idea that it could be a useful method of text composition. I wrote about it a little in What Is Steno Good For: Writing and Coding. I found the ease and fluency of steno incredibly freeing when I used it to write a novel. But I'd received my stenographic training in a formal school, and was already working as a professional stenographer. The real question was whether steno as a means of text input could be useful in an amateur context. Back in the early to mid-20th century, when steno machines were fairly common and machine shorthand could be taken as an elective in most high schools, people wouldn't tend to use it for text composition because the steno notes had to be tediously retranscribed on a typewriter, and it was more efficient just to skip the middleman and use the typewriter directly. From the 1980s through to 2010, only professional stenographers had access to computerized steno machines and translation software, and most of that software didn't interface easily with most operating systems, so without a fair amount of fiddling it couldn't be used to write emails, text chats, or other texts that weren't legal transcripts. Steno was for professionals, not amateurs. Steno was for transcription, not composition. There didn't seem to be many counterexamples, so these two principles somehow took on the force of dogma.

Now that Plover exists, though, just about anyone can learn steno and immediately start using it as a qwerty keyboard replacement. When I explain to people that there's a huge potential user base of people who want to use steno to compose text, I get all sorts of objections:

"Steno is too hard and tedious and takes most people years to learn."

"No one will want to invest the time necessary to become proficient unless they're hoping to get paid for it, and without professional-level proficiency, steno is useless."

"Steno is designed for transcribing external speech, not internal thought."

None of those arguments have ever held much water with me, and slowly but surely my hypothesis is being borne out. People are teaching themselves steno with our free online materials -- not in years, but months. Even though they start out slow, they gradually gain speed while using steno for basic tasks like chatting, writing blog posts, and working at their jobs. Here are a few accounts from people who've successfully incorporated Plover into their daily lives.

Harvey writes:

I got my Stentura 400 SRT off eBay intending to learn steno/Plover as a hobby, and I thought it would be cool if I got up to professional speeds, especially for my transcription work.

I started on the twelfth of May. At about five weeks I completed all the lessons in Learn Plover, picking up on little patterns as I went along. It was somehow easy to memorize the different strokes that make up all the sounds on the keyboard. Honestly, it feels like I breezed through it all. I'd go through a lesson and then I'd do an accompanying drill from Plover, Learn a few times. Then I'd just go through the previous drills to keep fresh. When I felt I was able to, I would try writing new single and multi-stroke words to get a feel for it. That's all there is to it.

I can now write at about 30 to 50 wpm, though the latter is only in bursts. It took me only two months to reach this point, and now I'm mostly just building speed and committing new words to muscle memory. I've enjoyed it a whole lot, too. It's really cool to write in a system that's so different than typing on a keyboard.

I've heard that some people insist that it's impossible to learn steno in two months or that it can't be self-taught. I feel I've proven that wrong; I learned the system to pretty good proficiency in eight weeks. I think anyone can self-teach steno, but the hard part is building up speed. On that I can't comment yet, but I'm sure it'll come with time and practice.

By the way, I wrote all of that using my steno machine.


Ted (who started learning steno nine months ago, though his update at one month is also pretty illuminating) writes:

I’m a learner of Plover on an ErgoDox, I type a little over 100 words per minute, similar to my QWERTY and Norman layout speeds, but the comfort is unmatched and the endurance that I can get out of typing this way is unbelievable. Not to mention that most spelling typos are impossible. (But the typos can be really funny. Like a valid typo for “awesome” is “awful” — just a one key difference. And “goal” can accidentally come out “grade school” if you don’t use the phonetic rules properly) So far the only big problem I’ve had with stenography is that I end up typing huge walls of text for no reason, because my hands don’t get tired and the speed doesn’t discourage my brain from continuing.


Charles writes:

I'm coming up on two years and I'm very comfortable now with steno. I use it for everything now, and have been for at least the past year. I think it took me about three months to be able to write anything I wanted. It really got good when I started to make my own briefs. I have a lot of little things to help with the unix command line and programming in Forth. I haven't really measured my speed either way, but I believe I'm equal to my old speed and getting faster and smoother all the time. More importantly, it's a lot less work now. My fingers don't have to do much! I love the way it feels. I think it's good for my brain too.


Clearly steno isn't just useful for professionals, and isn't just useful for transcription. It's possible to learn it fairly quickly and then to build speed naturally over time while putting it to use. We've just got to get the word out.

If you've had a similar experience to Harvey, Ted, or Charles, will you write me with a brief summary of how long it took you to learn steno and how you tend to use it over the course of your day? I'd like to compile a large collection of these stories that we can show to any naysayers who think that amateurs have no place in modern stenography.
Viewing all 512 articles
Browse latest View live