Bikini Body is In Print

 It's that time. All the changes are rolled in, Is are dotted, Ts are crossed, KDP is happy, and "Poltergeist! Bikini Body" has shipped. More info on my website at http://www.jamesrstrickland.com.

Bikini Body, the third Poltergeist! novel, is about what happens when Nina Cohen, a poltergeist detective in a human body, goes on vacation to a small vacation town on Lake Superior. Does she lie on the beach with a mai tai? Does she read a book? 

She does not. 

She gets into trouble, and winds up digging into a long-buried mystery involving a missing exotic dancer, a local scandal, and the legendary Lake Superior Mermaid.

I've also updated book 2, "Poltergeist! Dead of Winter" with advertising for "Bikini Body," as well as many fixed typos and so on, documented in the revision history in the very front of the book.

I've also updated the ebooks for "Poltergeist! Dead of Winter" and "Poltergeist! Ask the Dust" with their own CSS, embedded fonts, and all the goodness that the Kindle reader is so unlikely to let you actually see. I have my reasons. Watch this space.

KDP Covers and Affinity Publisher v2

A few things on doing KDP covers in Affinity Publisher:

1. Layer styles are where you style text for anything not text-ish, like leading, kerning, and so on. Layer styling doesn't kill the text into a graphic the way it does in some packages.

2. The document dimensions you give Affinity Publisher at setup are the trimmed dimensions, not the absolute dimensions. KDP is supposed to recognize the metadata in the PDF that tells it this, but surprise, it doesn't. So subtract twice the bleed from both the height and width of the absolute cover size (from KDP Cover Calculator) before feeding this into Affinity Publisher's page size.

3. Use frames to set component sizes. If you still need alignment lines, snap them to the edge of a frame, then move them. The delta value will give you the amounts you want.

4. Almost always, you want Duplicate Layer and not Copy Layer.

Does this suggest that Bikini Body is approaching publication? It does. I have prototypes of the paperback and hardback versions ordered. If they check out, we're good to go.

Toolchain Changes, Addendum

Two significant tool chain changes since my last post. 1. My day to day writing tool has become IA Writer because 2. My day to day writing machine has become a new (to me) M1 Mac mini. I'm pretty much done with Linux.

Also, I finished Bikini Body back in mid-August, and it's back from E.C., so I'm working through the change list. :). I expect to release Bikini Body soon. I'm also tentatively pulling together the plot threads of Nina Cohen 4: tentatively titled Ghost Light.

Toolchain changes

 Skimming back over my blog entries, I realize I left out something important—at least to me. In addition to switching to Obsidian on the front end, and Pandoc for first-stage back-end (it's getting complicated), I dropped LaTeX in favor of Typst.

What is typst, you ask?

Let me back up.

My goal is to write a novel once, and debug it once. This never happens.  

Instead, I write a novel in Obsidian (Markdown), turn it section by section into .docx for my writing group. They respond with the track changes and comments feature in Word, or any of the other word-ish programs they use. I use TextMaker for this. So I go through their comments and changes and manually apply all the changes, and any other changes I see fit to make.

Then, when the novel's done, I compile the whole thing into a .docx and send it to E.C. Tobler. She corrects and comments, and I go through the entire novel, all 392 pages for Dead of Winter, and implement her corrections and most (if not all) of her suggestions.

Then the fun really starts. Once the book is ready, I make it into an epub, which Amazon can digest into a Kindle book, and into PDFs, which Amazon can turn into MoD books. If you're keeping score, that's five different output formats: single-chapter docx for the writing group, huge honking docx for E.C., EPUB, pdf for paperback and pdf for hardback. (though the last two are identical except for the internal ISBN number.)

 Then, after I release it, I find typos. Sometimes they're editing scars, things I introduced during the preceding steps. Sometimes they're search/replaces run amok. Sometimes they're things I missed in E.C.s edit comments. Doesn't matter. The point is, I have to regenerate three of those five formats again.

If I were to typeset the PDF versions with conventional typesetting software (InDesign, Affinity Publisher, etc), change tracking would be the bane of my existence. Did I fix the comma on page 205 in both print versions? It would only get worse as I add more MoD houses and Ebook sellers. 

I have to have, must have, for sanity's sake, I need one source of truth for my novels, one place I can make a correction and propagate it to all the different output formats in a completely automated format. For me, that source is the markdown file.

Pandoc can translate markdown into HTML, and thence into epub in one step. I can control what it looks like, to the extent that the Kindle App respects what I tell it to do (not much) by twiddling the Pandoc template file and the CSS file. These are the same for all the novels in this series.

For the PDFs, I used to use LaTeX. LaTeX is ancient. LaTeX is vast. LaTeX is poorly understood. I've described writing LaTeX code as "write code, sacrifice a chicken, and hope for the best, and sometimes it just breaks, even with the same input." 

This is where typst comes in. Typst takes a markdown language (its own, naturally) and writes it out into pdf, according to code logic. In short, it does exactly what LaTeX does, except that it's new, written in Rust (so stability is good), well documented, with coding paradigms that don't seem like you need a grimoire to understand them No chickens need be sacrificed.

Even better, pandoc has support for typst. So I can make a change, bake the document together (from individual scene files) in obsidian, pandoc it into typst source according to a very customized template, and compile *that* into a PDF. This is repeatable. Which is good, because I wind up repeating it. A lot. For my hardcopy books, both Amazon at the moment, these come from one amazon 5.5x8.5 pandoc template. All the novels in the series should use the same template here, too.

Typst has a few warts. Like LaTeX, it tends to go bananas with hyphen-breaking words. You can turn that off. The biggest wart for me is that it does not yet have the ability to make page blocks in a spread the same length. In fact, its widow/orphan/slug avoiding code will *always* break equal page lengths any time it cycles. I'm looking forward to when they fix that. But I can live with it.

I see I've put the sly implication above that I might be releasing books through more venues than just Amazon/KDP. I have to lay some groundwork for that. Right now, my books all have Amazon ISBN numbers, among other things, and there are a lot of moving parts I have to take care of before I can fix *that*. Once I do, this toolchain will become even more important. Everyone's EPUBs are different. If I'm doing MoD, their formats are probably subtly different. With one source of truth, the markdown files, I can live with that.

Way more info than you wanted? Probably. But maybe it will help someone else trying to put together a similar toolchain. If you are putting such a thing together, and you'd like to see my template files, pop me an email or comment.

Links here:

Obsidian with the following plugins: Advanced New File, April's Automatic Timelines, Easy Bake, Enhancing Export, File Order, Force Note View Mode, Global Search and Replace, LanguageTool Integration, Linter, MonoNote, Note Refactor, Novel Word Count, Outliner, Shell Commands, Smart Typography, and Templater.

Pandoc

Typst 

Languagetool (The desktop server) 

Affinity Publisher (Which I use to typeset my covers)

Canva (Where I create my cover art)

Dead of Winter

New Book Out!

 

 I’m not your ordinary gumshoe. 

My name’s Nina Cohen. Born: 1898, died: 1912. I’m a poltergeist in a human body. I work from home as a private investigator. I watch entirely too much TV, and I talk to my cat. Say hello, Djinn.

Meow

My cop buddy Cronenberg talked me into this case. I’m just saying.

Nikita Zapata had everything to live for: friends, teammates, good grades, a volleyball scholarship to college. Then she went missing.

Jenny Thordarson had nothing: abused, trafficked from a young age, family history of drugs, you name it. She went missing last summer.

On the face of it, these two high school girls have only one thing in common: they were both Morgan Whitney’s best friends, and Morgan’s not talking.

My job was to find Nikita. There were fifty-thousand dollars in it for me. That’s why I’m undercover in high school.

Now I’m hip deep in ancient powers beyond anything I knew about, the spirits of serial killers, teachers that don’t like me, and snow. Lots and lots of snow.

Nobody said the life of a high school girl was easy.

 Dead of Winter, available on Amazon now!

Music and my books

 A novel is a big project. I plan each of the Poltergeist books to be in the neighborhood of 50,000 words and give myself about six months to write it. Over that time, each book finds a song on my phone that tends to pull it toward its conclusion. So for the Poltergeist books thus far, here are those songs.

Ask the Dust:
Anikin vs Obi wan
London Symphony Orchestra (John Williams)
Star Wars: Revenge of the Sith

There's a lot of betrayal in this book. Some is resolved peacefully, some is not.

Dead of Winter:
Love is Christmas
Sara Bareilles
(single) 

The harshest of the bunch so far, but it ends on a note of love. Really, that's kind of the underlying theme. Still working my way through editing this one. Hopefully I'll get it out there soon.

Bikini Body:
Angel
Sarah Mclachlan
Mirrorball

I'm only 20,000 words in to this one, so I'm not going to talk about the plot as though it's a done deal yet. Even the title's not a done deal yet. I set out with the theme being truth, but it's drifting toward bodies and family. We'll see what happens.

 

SoftMaker Office

I liked SoftMaker FreeOffice enough that I went ahead and bought SoftMaker Office.  After all the years of using never-quite-finished open source software, SoftMaker Office and FreeOffice have a level of polish that I'm not used to on my Linux box. (It fits right in on my Mac, and there's a Windows version too.)

The only serious complaint I have with TextMaker—the word processor—is that it doesn't have a wordcount field you can put in the document and have it live-updated.

Seriously?  Seriously.

Wordcount is readily available, right down in the status bar of TextMaker, and I can copy-paste it into the document readily enough. It's just weird that it's missing. That's been my experience with TextMaker (and FreeOffice) to date: works great, stable, but sometimes there's an odd thing missing and it takes time in Google to either find the allegedly missing feature, or devise a workaround. It also takes probably thirty seconds to a minute to load a 98000 word novel. This is acceptable, if not ideal. Once the novel is loaded, performance is fine.

Still. A hundred dollar one-time-payment for an office suite? Worth every dime. Strongly recommended.