As this incredibly dysfunctional and deadly year nears its end, I’ll close 2020’s posts on a personal note: it was a tough year for writing, at least for me.
Many wonderful novels, stories, poems and non-fiction works were published this year, to be sure. Yet I know I’m not alone in feeling the effects of distraction and isolation on my writing. When every day is “Blursday,” it’s tough to focus. Not to make excuses—one must try, and I did. I published a grand total of one poem and one story this year. (Actually, the story won’t appear in Gargoyle until next summer.)
So, not a productive year. I can’t blame it all on the pandemic. Part of the responsibility is mine—I should have found more and better, more consistent, ways to focus, and I didn’t. Part of the responsibility lies with a fundamentally flawed literary marketplace, especially the minor leagues of literary magazines and chapbooks. There are myriad problems here which will likely be the subject of a future post.
The one poem I published, “Criminal,” appeared in the Spring 2020 edition of Poetry Quarterly. I’ll reproduce it below, since its subject matter and especially its title seem relevant to the horrific year we’ve just experienced.
I know it was a crime at least as cold as the fluorescent light that bore down on my father’s deathbed.
But I still can’t grasp the betrayal, or the indifference that enabled it. No conscious thought was involved.
Dad had been declining for a year, dropping faster toward the end, life’s last, careless insult a needless broken hip.
It was the fall that did me in, he told me when I flew out to see him in San Jose. When I first arrived his head was thrown back
and his mouth gaped. It was awkward. He was propped up in the hospital bed, and later that day I spooned out soup.
He slurped happily, as though life hadn’t changed all that much. But then he knew again it had—his time was nearly gone.
You’ll stay with me? he asked, eyebrows raised. I can’t, Dad, I told him. I have to get back.
He died the next evening, after I’d returned home. Distance helped blunt the news.
Update, 1/30/21: there is a bug in the recent Scrivener 3 betas which prevents Scrivener from launching successfully after installation. You can resolve it by using winetricks to install speechsdk. This is now fixed.
It goes without saying that these are troubling times. Politics and the pandemic, bound tightly together in this dysfunctional country, will be with us through the end of this year and well beyond. So let’s focus on something small and potentially positive, only tangentially related to the larger world.
There aren’t many fiction writers who use Linux as a regular platform, I’d wager. Yet there are a few, including me. I believe that open source at its best serves as a role model for how the larger society should function. This quality in itself attracts some socially conscious creative people to the platform. The problem, of course, is that commercial software remains dominant, and not all of it can run on Linux. It is possible to write with existing open source solutions. But the best solution for aspiring novelists is the carefully crafted Scrivener, developed by a small, quality-focused software team at Literature and Latte in the UK. And Scrivener no longer runs natively on Linux.
To the company’s credit, a version of the Scrivener Linux beta remains available, and this can interface with the current Scrivener 3 on the Mac by translating documents from Scrivener 2 format to Scrivener 3, and vice versa. But the need to “translate” back and forth is a less than ideal solution.
For a while, Wine had come to the rescue—Scrivener ran just fine “out of the box” on default Wine installations. But that changed sometime back, as Scrivener 3 for Windows development evolved. Wine stopped working, and I turned back to Scrivener on macOS to continue work on my novel. Apple still leads the pack in terms of both ease of use and options for writers (but Linux exemplifies the moral high ground, as noted above).
Now that the new version (20.04.1) of Ubuntu LTS is out, I decided to take another look at the situation, and I have some good news for the small audience of writers on Linux. The latest beta of Scrivener 3 for Windows does run on Wine. You just have to do a little extra work to enable this.
A quick disclaimer: while I worked as a developer for many years, I now focus on writing. As a writer, I can’t afford to be distracted by any particular tool. If something doesn’t “just work,” I’ll find an alternative that does and concentrate on the writing. That’s why I hadn’t wanted to get down into the weeds to figure out all the nuances of enabling Scrivener 3 on Wine. But when I took a quick look, I discovered that things weren’t that bad. My Wine configuration is probably a little wonky, and I’ll likely do a complete reinstall when Scrivener 3 for Windows is officially released, supposedly sometime this fall. But getting the software to work again isn’t all that much work.
The latest beta, 188.8.131.52 (RC9), would seem to indicate that the official release is near (fingers crossed). The beta expires in mid-September. Here’s how to get it working.
If you already have Wine installed, you have two choices: you can create a new prefix for Scrivener, or you can update the parameters of the default .wine prefix. (I’ve tried both, which is why my configuration is not as clean as it should be.) If you don’t have Wine installed, then installing it should be your first step. It’s straightforward, and I won’t describe the process here.
If, like me, you only plan to use Wine for Scrivener and one or two related programs (Literature and Latte’s Scapple “brainstorming” software runs fine on the default Wine install), then I recommend updating the environmental settings for the default prefix .wine to meet Scrivener’s current requirements. The process described below applies to Ubuntu Focal but should be translatable to other distros.
The core requirements are Windows 7 or higher and .NET v4.6.2 or higher (Wine 5.0 will let you use .NET v4.8).
Once Wine is installed, make sure you have 32-bit architecture enabled. This is needed for various reasons overall, and also to register Scrivener. The command is:
sudo dpkg -i –add-architecture i386
Following that, run this:
Now you’ll need to install Winetricks. Again, this is straightforward. Once you have it installed, run the following commands. The first one is:
This is necessary for Times New Roman, the most popular font for submitting your work to publishers. If you already have the font on your system (it might have come with or been installed by another program), you can omit the above command.
env WINEPREFIX=$HOME/.wine winetricks win7
env WINEPREFIX=$HOME/.wine winetricks dotnet48
Now you should be able to right-click on your downloaded Scrivener 3 beta file and use Wine’s installer to install it.
Scrivener will create a .desktop file than you can use to launch the program (which didn’t work in my case, because my overall Wine installation has some issues—as I said, I’ll clean this up when the official version is released). You can then add the launcher as a “favorite” in the dock.
An easy alternative for launching is simply to hit the Super key to bring up Search and type in the first few letters of “Scrivener.” Once you see the program just hit Enter to launch it.
Or, if you like the command line, make a little shell script like so:
cd ~/.wine/drive_c/‘Program Files’/Scrivener wine Scrivener.exe
Then you can run it with:
from whatever directory you placed the script in. That said, a launcher is probably the best way to go and that’s what I’ll use once I clean things up.
And there you have it—a little work, but well worth it for those who want to be able to use the best long-form writing program on Linux.