Looking for writing-related posts? Check out my new writing blog, www.larrykollar.com!

Tuesday, August 16, 2016 3 comments

CreateSpace Cover Calculator (Tech Tuesday)

To be honest, I’m surprised that CreateSpace doesn’t have something like this on their own site already. Any time you want to publish a paperback with CreateSpace, you need to include a cover (or pay them to make one for you). The DIY guidelines include a formula for calculating spine width, based on the number of pages and what kind of paper you’re using. But even if you’re decent at math, and I am, it can be nerve-wracking enough to double-check and check those measurements again.

Now if there was a way you could feed your page size, number of pages, and paper type to a calculator and get a no-sweat measurement that you could use for that cover…


Oh. Just look to the right. Over there in the sidebar. I’m no JavaScript whiz, but I had a clear idea of what I wanted to do and there’s plenty of information online. I had the thing going in not much time, which surprises me all the more that CreateSpace hasn’t done it. It’s been around for a month or so now, but I figured it was a good topic for Tech Tuesday.

The “Page size” dropdown lets you choose from all the standard CreateSpace sizes, plus a “Spine Only” selection if you’re using a custom page size. The widget automatically adds the 1/8" bleed to all four sides of your cover, expands to show the results, and collapses again if you click Reset. The rest of it should be self-explanatory.

Feel free to drop by and use the widget any time you need to calculate a cover. If you want your own copy, that’s fine, too. I released it under a Creative Commons attribution/share-alike license, which means give me credit and pass your changes on so all indies can benefit. Then again, I’m not sure what else it might need… except maybe a way to select Lightning Source.

Sunday, August 14, 2016 3 comments

The Great Closet Purge of 2016

I’ve been saying for a while now that I need to get clothes I don’t/can’t wear out of the closet to take to Goodwill. Well, today the wife took Mason to see The Secret Life of Pets, leaving me with Charlie. The baby was ready for his nap, but wasn’t about to go to sleep while Mason was making noise and doing amusing things… but it took less than 10 minutes to put him down once they left. With him asleep, and me alone and stuck in the manor, I decided this would be a good time to tackle that closet.

Now I figured to purge enough clothes to fit in one bag, then I could run by the Goodwill dropoff after dropping Mason off at school. But the Great Closet Purge of 2016 had other ideas. After taking a third of the old shirts out, I already had two stacks and wasn't even half done with the closet. Next came the pants; over half of those had to go, but I found 8 or 9 pairs I could wear and didn’t know I had. Finally, the sweaters and miscellaneous stuff on the floor. I ended up with four stacks, plus a separate pile for rags. Then Charlie woke up.

Note: the baby is to show scale and isn’t otherwise part of the purge.
Somehow, I don’t think I‘ll get all that into the Miata with room left over to carry Mason and his bookbag. Besides, I have to purge my dresser as well…

Monday, August 08, 2016 3 comments

Lucky 7 (Months)

Hey, put your finger in here…
Charlie’s 7 months old today. As you can see, he has been cutting teeth for a while. This of course is accompanied by the usual “chew on anything kind of soft” thing that babies do. If you give him a finger, he’ll s-l-o-w-l-y pull it up to his mouth, touch it to his teeth, then start applying pressure. And those teeth are sharp. At least he gives you plenty of warning.

He’s not sitting by himself or crawling just yet, but I can no longer drop him on my bed between two pillows and expect him to stay put. Saturday afternoon, he wriggled out from between the pillows (in his sleep) then flipped over while I took care of some laundry. Fortunately, he didn’t go any farther. Now I know I can’t get away with doing that anymore.

We’re converting the wife’s office, a tiny bedroom really, into his room. That entails moving a bunch of furniture around, as always. Mason’s big enough to help now, which should make life a little easier. The office stuff will go into the corner of the living room where Charlie’s bed (and some other stuff) is now.

Diamond sword something something creeper…
His surrogate big brother Mason is obsessed with Minecraft these days, but he’ll always make room for Charlie to sit and watch. Mason’s always ready to clown around for Charlie, who always appreciates his antics and weird noises.

Charlie, of course, has a bit of clown-sense of his own. Sometimes when I'm giving him a bottle, he'll catch my eye, grin around the nipple, and go “hee heeeee.” That cracks me up, which gets him going, and it turns into a positive feedback loop. Usually, when he does that, he’s had enough bottle anyway.

Stay tuned… always something weird around FAR Manor.

Tuesday, August 02, 2016 No comments

Tech Tuesday: Getting Your Outline into Scrivener (pt 2)

In last week’s post, we saw how you can import an OPML outline directly into Scrivener. For those of us who use an outliner for more than the barest-bones plotting, it’s rather limiting. Fortunately, Scrivener has another way to import. It requires an extra step, but Tines (the console-mode outliner I use and maintain) can do the work.

So let’s go…

No Extensions Required

OPML entries have a type attribute associated with them. The standard deliberately leaves the content of type undefined, except it’s some kind of text to describe the entry.

Tines supports two type definitions: "todo," to give an entry a checkbox, and "text" to mark entries as content (non-text entries are assumed to be headings). Tines assigns the F3 key to toggle between text and heading types. A lowercase t to the left of the bullet gives a visual indication. So now, let’s add some more info to the first scene:

Nothing like a little slapstick to start a story, huh?
Note the t at the beginning of each entry under Scene 1. Those are text entries. Other entries will become documents in Scrivener.

Now here’s where the magic happens. In Tines 1.10, there’s an Export->XSLT function that allows exporting through xsltproc. Since OPML and Tines’s native hnb format are XML files, it’s easy to convert them to just about anything. Press ESC to bring up the menu, and go to the File menu…

Changes to the look and feel are due to experiments with the configuration.

Scroll down to Export->XSLT, press Return, then press M at the next prompt to choose Markdown. When prompted, enter a name for the Markdown file (I used storymap.md). If you want, have a look at the Markdown file to see how it does things—a # character at the beginning of a line is a heading, and the number of # characters says what level heading it is. Other lines are body text. Easy, huh?

Now let’s load it into Scrivener. There’s two ways to do that.

Import and Split

I don’t really recommend using File→Import→Import and Split. It works as advertised, importing your Markdown file and splitting it up, but it doesn’t build a hierarchy. It might be useful for importing an outlined chapter into an existing project.


Import as MultiMarkdown

MultiMarkdown is, as one might guess, an extended version of Markdown. Since it’s an extension, you can import plain Markdown as MultiMarkdown without a problem. So try File→Import→MultiMarkdown File instead. Here’s how it looks:


Now this looks pretty close to what we want! Everything is in a nice hierarchy, content is content, and we’re ready to get the story knocked out.

Until next time… keep writing, and keep geeking!

Monday, August 01, 2016 1 comment

Giggle Fits

Yesterday afternoon, after a lawn-mowing session, followed by some fixes and improvements to Mason’s slide and climbing wall, Rosie the Boston Terrible was moaning and woofing at the thunder coming in. Charlie thought that was highly amusing, but that was nothing compared to when I started making fake thunder noises myself.




I thought *I* was easily amused.

Tuesday, July 26, 2016 1 comment

Tech Tuesday: Getting Your Outline into Scrivener (pt 1)

Part 1 of a two-part series

I’m a pantser by nature. I like to get the story started, then let the characters tell me what happens. But that doesn’t always work. Sometimes, in the heat of composition, you get ideas for side-stories, sequels, and completely different worlds. You can sometimes placate the plot bunnies by giving them a little attention, taking down a few notes and promising to come back when the story at hand is done. Of course, an outliner is one of the best ways to organize notes and plot a story—in the 8-bit pre-DOS days, an early vendor was pleased to call their offering an “idea processor” (and an outfit called Axon uses that label for their mind-mapping tool today).

Scrivener’s Binder pane can be used as a crude outliner. But when you’re trying to bang down some ideas before you forget them (or get distracted by a family member), you want the speed and smooth operation that you get from a dedicated outliner or mind-mapping tool1.

Fortunately, most outliners and mind-mappers support OPML (Outline Processor Markup Language), a very simple XML document type—and so does Scrivener, at least for import. So you can knock out your outline in your favorite outliner or mind-mapper, export as OPML, and pull it right into a new Scrivener project with the hierarchy in place.

Tweaking Scrivener

Before you import, though, you should review Scrivener’s OPML Import settings to make sure they’ll work the way you want. Open Scrivener’s preferences and follow the red numbers:

There’s not much to change. Creating a folder is needed only if you’re importing notes rather than your story line. If you have a “root” entry, with everything else as a lower-level entry, then you already get what amounts to a new folder.

Dealing with notes may or may not be an issue for you. The commercial OmniOutliner added a “note” extension to OPML, for reasons unknown to me, and other outliners (including Tines) now include at least token support for it. Creating a note, and telling Scrivener to import them into the main text of each document, is the only way to pull in content (other than chapter and scene names) using OPML import. Other options are to put notes only in the synopsis, or add them to document notes.

Pulling It In

Maybe an example would help. Thus, a generic story called The Importing, a slightly filled in outline (Trevor McPherson’s StoryMap for Freemind, converted to OPML for this job). I added a note to the first scene in Tines, using an experimental OPML-centric configuration file:


The note content is at the bottom of the screen. Internally, notes use a _note attribute, in parallel with the entry text. Imported into Scrivener, we get something that looks like this:


As you can see, every entry in the outline becomes a document. Notes are extremely limited for writers who want to put in more than one line of content in a scene. I don’t know about anyone else, but I often want to add bits of dialogue, maybe some descriptions of the setting, who’s making an appearance, how the scene wraps up… you get the idea.

Fortunately, there’s another way to get your outline into Scrivener, one that lets you include all the content you feel like adding in the outliner. We’ll take a look in Part 2.


1Think of a mind-mapping tool as a graphical version of an outliner. Each entry is a bubble, centered around a root entry, and can be arranged to suit your needs. Freemind is an open-source example, and runs on all platforms (needs Java though).

LinkWithin

Related Posts Plugin for WordPress, Blogger...