New readme file!

So the illustrious Stan, longtime Plover user and supporter, has turned the ugly-as-sin Github readme file into a gorgeously formatted PDF. He also assigned it a version number, which I'd been extremely neglectful in not attending to up 'til now. Behold!

Plover Readme 1.3

Thanks, Stan! You're the best. Hopefully in the not too distant future we'll be writing a whole new extensive readme to incorporate the keyboard emulation features that Josh, Plover's lead programmer, is currently working on.

Edited to add Stan's reply in the comments, just because it's too good to be overlooked by people who might not click through:

Well, it ain't open source for no'n ;).

I definitely had fun doing it -- even though it distracted me from actually practicing steno along with the fact that I stayed up until nearly five in the morning to do it. But I figured this would be easier than the old readme file which I for some reason I had a hard time following (maybe I was the dummy toward which the dummy series are directed).

But I'm glad I could contribute. I hope the version number makes sense. My reasoning was as follows:

1.0 - Plover that worked in command line.
1.1 - Plover that opened the small window (for which you made the 'it really works!' video)
1.2 - Addition of Eclipse and DC dictionary support
1.3 - Current one with the text output and GUI.

On a final note, I want to let everyone know that everything in that readme is subject to change and revision. I threw that logo together because it was the first idea that popped in my mind but again, I can design something a lot sleeker if I spend a little more time thinking about it. But I do love the designs from the design prototypes post so I will do my best to try to somehow integrate them if I decide to change it up.

And of course with any major changes with Plover will hopefully be documented in the readme.

I'll put up a url for the original InDesign file once I get my FTP server working again (home ISP services tend to look down on mass file sharing I have found) to uphold the opensource spirit.

Go Plover and opensource software! I'm pretty much done shoveling through my backpack for the hardware key every time I have to open CaseCATalyst or having to spend $5k on Eclipse once I go pro. Many people at my school and around Seattle have even expressed interest in learning steno after observing me practice at coffee shops or libraries. They say, "How is it that you're 'typing' THAT fast?" Or, "My fingers and wrists would kill me if I even attempted half of that pace on a regular keyboard." Then I begin to explain how it works, show them my theory notes, and tell them that I was doing a 200wpm drill and they become captivated further. Once I tell them how much machines and software cost however...

Makes me wonder how many people we could get to at least give steno a chance if the equipment were more accessible.

Steno machines and software are really not complicated things. It's only because of its esotericism that companies are able to reap in as much as they do and bully their users around with excessive and cumbersome anti-piracy measures for technology far exceeded in complexity by things as common as the iPhone or a netbook PC.

With everyone's small contribution I think Plover's really got a chance to rise up to become an equal competitor along side DC, Eclipse, CaseCAT, etc.

Linux did. It even runs on mobile phones. Who's to say we can't steno on an iPad or on a tablet PC?