Sign up for my newsletter to receive news and updates!

Posts Tagged ‘in ashes lie’

A day late

I meant to post this after getting home from ICFA last night, but got distracted. Eighty days seventy-nine days to the publication of In Ashes Lie, and today’s bit of added content . . . comes from Midnight Never Come, actually.

Long-time readers of this journal may recall that back when I drafted that book, I had to re-write a substantial chunk of Act One — basically Deven’s chunk of it, almost in its entirety. Therefore, in the spirit of the “deleted scenes” they put on some DVDs, you can read the original draft, complete with some notes about why it got replaced (and what I wish I could have kept).

There’s mild spoilers for MNC in the discussion of those scenes, so if you want to say and/or ask anything about them, I direct you to the spoiler thread for the novel; comment there instead of here.

Ninety days . . .

. . . and counting.

Since I’m aiming to spread the exciting content (i.e. the excerpts) out a bit, this time you get something a bit more dull. Unless you’re one of the people who apparently loves hearing me geek about the historical research, in which case, my research bibliography may count as very exciting indeed.

If the Midnight Never Come bibliography is any example, that list will continue to grow as I keep remembering other books that should be on it. But at least it’s something to start with.

One Hundred Days . . .

. . . and counting.

As with last year, I’m going to dole out bits of stuff to keep you all interested between now and the release date of In Ashes Lie, on the tenth of June. Expect something every ten days, assuming I can keep myself organized enough to put everything together, and alert enough to post it when the appropriate day rolls around.

Today? You get your first taste of the book.

More icon love needed

I still haven’t gotten around to figuring out how to do text-on-images in a pretty (i.e. more than basic) fashion, so can anyone take the cover in the last post and make me a proper Ashes icon? Something in the vein of the MNC icon, seen here. The font used is AquilineTwo, which you can get for free online.

collected writing news

Small bit first, since otherwise it will vanish next to the other news: Shroud Magazine has purchased my twisted fairy-tale retelling “Tower in Moonlight.” (This is part of the ongoing set that includes “The Wood, the Bridge, the House”, “Shadows’ Bride,”, and “Kiss of Life.”)

***

Much bigger bits, relating to In Ashes Lie:

I actually meant to post this days ago, but it clean slipped my mind — the Science Fiction Book Club has picked it up as a main selection, as with Midnight Never Come, so those of you who got the last book in hardcover can do so with this one, too.

For the other bit, you’ll have to look behind the cut . . .

Nomenclative confusion

My poor copy-editor, dealing with London place-names. Fully half the queries on this book go something like this. “St. Laurence Jewry” — do you mean St. Laurence Pountney? “St. Giles Cripplegate” — do you mean St. Giles-in-the-Fields? “Aldgate” — do you mean Aldersgate? No, no, and no. Last book, it was people names instead; she kept double-checking to make sure this Edward whoever was not supposed to be that Edward whoever.

I’m glad she does it, of course. One of these days I will name two St. Laurence parishes when I only mean to name one. And to be fair, it took me a remarkably long time to sort the two St. Gileses from one another, and to figure out where each one was. But the queries amuse me. If this were a secondary-world fantasy, I wouldn’t repeat names half so often as the real world does, precisely because of this confusion.

Writer, Trust Thyself

Here’s the other thing about doing this copy-edit:

I have to trust I got things right.

Where by “things,” I mean the historical details. At the time I wrote these scenes, I had my research fresh in my mind, with notes and books open on the desk in front of me. That? Was last year. Do I still remember everything? No. And it’s worse with this book than it was with Midnight Never Come, because in this one, the plot engages much more directly with historical events — giving me oodles of chances to screw up. I could try to look it up again, double-check everything, but the library books have been returned and that would make the copy-edit take two months anyway. I have to trust that I got the details right in the drafting and revision stages.

Having said that . . . I’ve caught a few errors. But only because something stood out: a lack of a preposition in a historical quote, which made me check to see if that was a transcription error on my part, or the actual phrasing of the original. (Answer? Both: I have two books that give the line, and they don’t match up. I chose the clearer of the two.) Or me calling a character “Lady Elizabeth,” and then wondering if that’s the proper address for someone of her rank, which made me double-check whether I was right about her not being a countess yet. (Answer? She was a countess, and I had the address wrong. Also, I erroneously referenced her father, who was dead by then. Apparently I was asleep at the research wheel when I wrote that scene.)

I can’t check everything, though. I’ll have errors that crept in during revision, during drafting, during research when I failed to look something up in the first place. And some reader, somewhere, will spot them.

But you know, I’m okay with that. (Mostly.) Because the only way to avoid it is to have my characters float through a non-specific world, where events don’t have dates and buildings don’t have floor plans and the only people with names are the ones important to the plot. But that isn’t how real people live: the world you inhabit is concrete, specific, full of detail. You know the names of the people you work with, and sometimes they have walk-on parts in the story of your life.

What will be interesting to see is what this does to my secondary-world novels, next time I try to write one. Historical fiction has forced me to pay attention to the specificity of real life; can I maintain that specificity when I’m making it all up? I hope so.

At least nobody will be able to tell me I’ve gotten it wrong. 🙂

Thoughts from the Copy-Editing Mines

I managed a while ago to teach myself the distinction between “that” and “which” — I couldn’t tell you when each one should be used, but my copy editor has corrected me on it only twice so far in this novel.

On the other hand, I still haven’t mastered the “farther” and “further” thing. On the other other hand, the Fowler quote given in this Slacktivist post validates my tendency to use “further” for everything. I’m happy to let me CE correct me on it, but hey, at least I’m not totally off-base.

Speaking of off-base-ness, one of these days I’ll figure out where I got my notions of hyphenation from. My CE disagrees with me quite frequently on that stuff.

It still saddens me to watch these books being corrected to American spelling. (“Corrected” because random bits of my spelling are British. I blame a childhood of reading Diana Wynne Jones?) It just seems wrong. Especially since the US and UK editions are printed from the same edit.

Of all the epigraphs I chose for this book, I think my favorite is the one taken from transcripts of Charles’ trial. It’s a brief exchange between him and Bradshaw, the Lord President of the High Court of Justice, arguing about the House of Commons and the jurisdiction of the trial, and while it was almost certainly not what Bradshaw meant to say, it kind of sums up the entire damn period for me:

The King. Shew me that Jurisdiction where Reason is not to be heard.

Lord President. Sir, we shew it you here, the Commons of England.

Back to the mines.

Progress of the Report

Am off to a roaring start. This is deliberate; I habitually work out how much I need to do each day in order to meet my deadline, readjust it to create a margin of safety, then push myself to overshoot the readjustment. It’s how we make deadlines work, here in my brain.

I should note, btw, that I misspoke slightly when I said the late arrival of the CEM was due to a mixup on my publisher’s end; I have a tendency to use that phrase to signify anything that isn’t my end, which is inexact. The mixup was on the part of the copy-editor. But it’s the same copy-editor I had for Midnight Never Come, which pleases me; I like continuity, and I like getting a little note from her saying she’s enjoyed reading these books. 🙂

Anyway. I’ve done all the mechanical work scheduled for today, and then some; I’ve about hit the limit of my usefulness on that front. (Brainpower, not time, is the real constraint on copy-editing speed. It doesn’t do me much good to read over the ms if I’m zoning out while I do it.) I have a small list of revision-y things to do in these pages, but I’ll leave them until later tonight, when I’ve regrown a little of my attention span. And then maybe go over some more pages, because we like being ahead of schedule, yes, we do.

You know who likes it even better? My publisher.

State of the Swan

CEM is here.

Deathmarch has commenced.

I will either be silent for the next week as I try to plow through this at top speed, or posty like a posty thing as I find myself in desperate need of breaks from the work.

small favors

It isn’t actually a good thing that some confusion on my publisher’s end means my copy-edited manuscript isn’t here yet, but as it turns out, I’m just as glad; being dilated at the eye doctor’s renders me more or less useless for anything that involves reading. I’m managing this post, but it’s hard, and to read print I pretty much have to take off my glasses and hold the page two inches from my nose.

And my current Netflix haul is all subtitled, natch.

Today’s kind of shot, I’m afraid.

rereading myself

My copy-edited manuscript is expected to arrive tomorrow, and so I spent much of today re-reading In Ashes Lie.

I’m pleased to report that I like it, after all.

You’d think that would go without saying. But I spent so long head-down in this book, and so much of that time under a series of unpleasant stressors, that I truly lost my perspective on it. It’s the longest book I’ve ever written by a margin of nearly twenty thousand words, and approximately 87% more plotty than its closest competitors, which meant I had a difficult time holding the entire thing in my head at once; by the time I finished revisions, I was making changes half-blind, trusting to well-trained instinct that what I was doing would actually work. For all I knew, I was creating a Frankenstein monster of a book. But now, with the respite of having not looked at the thing for over two months, I find that — while there are some rough edges around those last-minute changes — on the whole, the thing works.

(Even the sentences, mostly. I can pay close attention to those in short stories, but in novels they tend to happen on autopilot, while my brain wrestles with plot and character and so on. Especially in a book like this. My autopilot, however, has gotten much better these last few years.)

Don’t get me wrong: I still don’t ever want to wrestle again with the fire-breathing hydra that is seventeenth-century English politics, and I still think this book deserves its moniker of “the Beast.” But that’s the voice of the months spent writing it, not the voice of the result. I don’t love it in the same way I love Midnight Never Come — no two books are ever the same — but I honestly believe Ashes has both Giant Spectacle and character moments that far surpass the best I was able to pull out for its predecessor. (The whole “burning down London” thing helped with the former.) It is a book I can be proud of.

And that two-month respite means I (hopefully) have the will to slog through the CEM, which is my last chance to catch any errors, polish those rough edges, and fix the sentences the autopilot did a less-than-spectacular job on. The production department appears to allot the same amount of time for copy-editing regardless of book length, so I’ll have to stick to a pretty rigorous schedule to get it done. But I’m actually looking forward to starting, at least.

(Ask me again in a week how much fun I’m having.)

Yes, they really did all of these.

“The 10 Most Insane Medical Practices in History.”

Reading that reminded me of one of the unexpectedly difficult things about writing Ashes: dealing with Jack as a doctor. The character is an intelligent, inquisitive man absolutely dedicated to practicing the best medicine he possibly can — but let’s face it, the guy lives in the second half of the seventeenth century. His idea of cutting-edge medical science is using Harvey’s discovery of the circulation of the blood to improve bloodletting techniques.

Jack is probably my favorite character in the whole book, but I wouldn’t let him within a hundred feet of me if I were sick. And yet I had to write lines describing how he’s trying to save somebody’s life by way of techniques that probably made things worse.

Note to time-travellers: if you ever get thrown back into European history prior to, say, the twentieth century, you’re better off refusing a physician entirely than letting one of them treat you. The body has this lovely thing called the immune system, and it stands a better chance of saving your life than any of them do.

my brain = sieve!

I meant to post this on Thursday. That tells you something of the state of my brain. (Hey, at least it didn’t fall by the wayside straight into 2009 . . . which some other things in my inbox are in danger of doing.)

If you have not much time for reading, but you do have time for podcasts, check out Beneath Ceaseless Skies‘ audio department. You can download individual stories — including, oh, say, “Kingspeaker,” which went up on (you guessed it) Thursday — or subscribe to the RSS feed, or get updates via iTunes. Instructions for those methods are behind that first link.

Now I’m going to go put on some music. Because while it amuses me that my mental stereo put on the Hallelujah Chorus when my editor told me she liked the revisions I did on Ashes, I’d like something different now.

revisions are off

The next day Mr Earbrass is conscious but very little more.

I’ve survived another round with the Beast*.

Time to watch back episodes of House online or something.

*Being The Novel Formally Known As In Ashes Lie But Frequently Referred To As Please God I’ll Be Good Don’t Make Me Deal With Seventeenth-Century English Politics Ever Again.

the state of the revision

Warning: graphic metaphor ahead.

***

I currently have the vivisected body of Part IV lying in front of me. (Figuratively speaking; I’m working with an electronic file, not one of my cover-the-floor-with-paper stunts.) I’ve sliced it open and gone to work moving things around: transplants for a few organs, repairs to others, a bit of experimental reconnection that I’m hoping will work. Generally, I feel good about the changes. Having it lying there all bloody is making me nervous, though, because this revision is due on the 17th, and I’d feel a lot better if I could stitch this part up and get it on its feet again, so it can walk around a bit and tell me if anything isn’t functioning the way it needs to.

I can’t, though, because it doesn’t have a liver. There was one before, but it never worked all that well — just well enough to pass — and I’m pretty sure it can’t handle the load the new transplants will place on it. And while a liver isn’t so vital of an organ that you’ll keel over on the spot if yours is kind of gimpy, it isn’t an appendix, either; we really want one that works. So I need a new liver, and I need it in the next week. And I can’t go stitching up the body until I have one, because I’d just have to cut it apart again to put the thing in, and besides, there’s stuff that needs the liver to run right. Which means I’m increasingly fretting about how much work it’ll take to stitch the body up again, and how frantically I’ll have to work to get that done once I have the damn liver.

Fretting, in case you were wondering, is not good for productivity.

There are other things I can work on, and I’m going to do those, so I don’t have to do them post-liver transplant. But it’s harder than usual to trust my usual work pattern — namely, that the idea will show up by the time I need it. Generally it does, and I know from experience that I’ll get better results if I relax and let the hindbrain do what it has to. Unfortunately, that doesn’t silence the little voice whispering but what will you do if it doesn’t . . . .

I’d feel a lot better if I just had the goddamned liver already.

Dear Brain: I’ve had a stressful year. Please don’t add to it any more than you have to. (And consider very carefully what goes on the “have to” list.)

Off to work, while I wait for the liver to arrive.

hah!

[EDIT: At the advice of my commenters, I’m putting in a notice that this is a post about revision, not politics. I’ve apparently given a few people minor heart attacks already, before they got far enough in to figure out what I was talking about.]

I said it all the way back in July: “When in doubt, throw in an assassination attempt.”

Now, the attempt in question ended up being canceled, but I think putting one in elsewhere may in fact be the solution to one of my problems.

Send in a man with a gun. I don’t think I’ll have an actual gun, but the advice still holds. Funny how this whole “learning your craft” thing involves coming around to the basic lessons over and over and over again.

aneurysm time

And now I have to disengage my brain from thoughts about modern America and participatory democracy and post-racism and the disintegration of the conservative movement and all that stuff, and go back to thinking about the philosophical underpinnings of seventeenth-century monarchy.

Brain. Hurty.

conversation with the brain

Conscious Mind: <singing> Revise, revise, revise the book . . . .

Subconscious: Oooh!

Conscious Mind: Yes?

Subsconscious: This is what the book’s about!

CM: Yes, we know that.

SC: Nononono. I mean, yes, but think about this.

CM: I did. Months ago. And that’s about as far as I got.

SC: Get ready to go farther. What if [spoiler]’s motivation was Y, not X?

CM: !!!

SC: Uh-huh.

CM: OMG. That works. So well. And it fits with the —

SC: Uh-huh.

CM: Not sure where to first bring it up, but we can totally work that here, and all through this bit, and —

SC: <preens>

CM: . . .

SC: What?

CM: Except that we resolved that conflict based on the assumption of Motivation X. Just how is this supposed to work out if it’s Y instead?

SC: . . .

CM: C’mon. You got me started down this road; you finish it.

SC: <ninja vanish>

CM: I hate it when she does that.