May 25

Storyist script again

Just a note if you downloaded the script and tried to get it working yesterday. I’ve made the following changes to the script this morning, so you will want to grab a fresh copy (see the Storyist to Google page for link and directions).

  • [Critical] Corrected a bug that was causing the script to re-copy your text every time it ran. Why critical? Because this meant that the timestamp on your file was always nowish, which could throw off the Google scripts from catching and processing the file.
  • [Minor] Added a somewhat convoluted attempt to remove extraneous whitespace from the file we generate into Google. With really large projects, this can help reduce the size of the file, plus it makes it easier for the diff scripts if they don’t have to compare all of your whitespace too.

If I was smart, I’d put all of this into github so you could track changes, instead of having download  links off of my dropbox account. That would be smart. Too bad I’m not so smart.

Also, it appears there are limits in Google, and I’m hitting them all trying to get the Google scripts to process my draft. At 90k+ words, it seems it takes longer than Google allows for script execution. And when it does run? The email it generates is too big.

May 24

And now how to get Storyist wordcounts into Jamie Rubin’s google scripts

Just a quick note while I slug away at revisions (Which, by the way, means my word counts suck, no matter how much I write, on account of all my deletes. Go figure.). Because of the pending move, and the fact that the good folks over at Scrivener have announced that it’s going to be –  yep – another two months while they track down internal bugs, I decided to dust off my copy Storyist and port the novel into it.

And by port, I mean deal with the fact that despite claiming to support Scrivener files, Storyist does a real lousy job of importing them in a usable format. You can see them, edit them, etc., but they aren’t considered manuscripts. It’s almost like they’re competitors or something.

However, Storyist, for all its faults, does have a rock solid integration with its iOS app. And with me looking at spending a day on a plane, I’d rather lug around an iPad than a laptop (cramped seats, big guy, it doesn’t take a math genius to know that tray table isn’t coming down all the way, which means that laptop has nowhere to rest). But using Storyist, with it’s Yet Another File Formatting, means I don’t have an easy way of updating my wordcounts via the @jamietr scripts.

So, I fixed that. It’s not much of a shell script – we don’t have to make any changes to how Storyist synchronizes, we just need to extract a file, clean it, and copy it over to Google. Jamie’s scripts pick it up and run with it, and all is happy (minus my note about too much text in one file, but that’s true no matter where your text comes from).

Storyist to Google (Mac)

Category: Writing | LEAVE A COMMENT
May 18

Psalms of Isaak Readthrough – Lamentation | Ken Scholes

Ken Scholes is doing a listen-through of his series as he preps to finish the last book. He’s promised us a review after he finishes each of the books. If this first one is any example, it should be an interesting series of blog posts, both for the behind-the-scenes and what’s on his mind then and now. For example, today I learned he’s a discovery writer (“pantser”) :)

On September 11, 2006, I took the short story about Rudolfo finding the metal man and pasted it into the document.  Then I took the second short story about the trial of Sethbert and did the same.  I converted that text to red so I would know to check it carefully and make sure it syncs up.  Then, without an outline and with only the vaguest sense of a war over Windwir erupting and culminating in a war crimes trial, I started writing.  I would love to learn how to be more of a planning/outlining writer but for most of this series, I’ve been discovering it as I go.

Source: Psalms of Isaak Readthrough – Lamentation | Ken Scholes