Whose thing is this, anyway?

I’ve blogged about possessive formation several times here, and I’m going to do it again. This time, I want to focus on those situations where a thing belongs to more than one person, either separately or jointly. This might be a physical thing, like a house or a car, or an abstract thing, like death or success.

Let’s say that in your novel, two people are killed in a car wreck. Perhaps there is a sentence like “Blake’s and Rhonda’s deaths could have been avoided.” Why is that genitive marker on each name? They didn’t have joint possession of one life, so they can’t possess a joint death, either. Two lives, two deaths. Each name gets the marker of the apostrophe and the S. Even in the case of conjoined twins, there are separate lives and separate deaths. Close together, yes, but separate.

[DISCLAIMER: I am aware, particularly in the medical writing/editing field, that there are different ideas about the phrasing of such things when it comes to “our hearts” or “our health.” That’s for the medical writers and editors to be concerned with. Me? I edit fiction. That’s my focus, now and always.]

Now, what about two people who jointly own a single item? “We were invited to Ben and Jerry’s house for dinner.” (Not just dessert, DINNER!) They own the house together, the same way they used to own their company.* The marker goes on the second name. If there were more people in the list, the rule would be the same; the marker goes on the last name in the list, if everyone owns the item together. “Bob, Carol, Ted, and Alice’s bed hadn’t been properly made in weeks.”

It’s not difficult if you take a moment to consider how the item or concept is shared or owned. If the people in question share it, possess it jointly like the house or the bed in the previous paragraph, only the final name in the list gets the genitive marker (apostrophe S). If they each possess (or are connected/related to) a thing singly, like the deaths in the first paragraph, each name gets the marker.

 

 

*You’re not going to catch me. They sold (some say sold out) to Unilever back in 2000.

 

PerfectIt 4: YES, you want it!

I’ve been going on and on about PerfectIt since I bought the previous version. It’s NOT a spelling or grammar checker. It’s a proofreading tool. You’re worried about inconsistency in hyphenation? PerfectIt has your back. Concerned about capitalization? No worries. What about acronyms being used without being defined? They’re covered.

(Full disclosure: I’m being compensated for this review. And no, it had nothing to do with that whisky bar in Providence. The agreement was made before that.)

(And another thing: This review is for the Windows version. If you’re on a Mac, you might like to know that this is catching us up with things you’ve already had!)

I’m not a power user. I wasn’t one before, either. My work is very simple compared to that of many of my colleagues. I don’t work with tables and figures. I don’t have to deal with footnotes or endnotes. No indexing. No tables of contents. No styles. (Sounds like I’m quite the slacker, doesn’t it.) However, I can still speak to how PerfectIt 4 helps with my work.

The most recent project, the one on which I was able to take this baby out for a test drive, had around 50,000 words. I opened the file, clicked “PerfectIt 4,” and unchecked the boxes of the tests I didn’t require (figures, tables, and so on). Then I clicked on “Launch.” (This is no different from the previous version. But …)

Within seconds (seconds! not minutes!), the program was ready for me to proceed. And this time, instead of my having to look at every instance of a change by clicking into the file location to see context, the context was right there in the box! That was magical for me. Instead of having to bounce back and forth to check each instance of “it’s,” for example, I could just click the radio button next to each one I wanted the program to fix.

One. Click. WOW.

The same was true of hyphenated compounds. I follow the guidance of “hyphenate before a noun, style open elsewhere” so again, it was a time-saver not to have to keep bouncing back and forth. One click per change I wanted to make. Boom. Done.

Sure, that doesn’t sound like much. Seconds? What’s the big deal? Multiply those seconds across all the projects you do in a year. It’s a clich√©, sure, but: They add up. They save you time. (And annoyance, if you’re working in a 100,000-word file.)

I was using the beta version, because along with agreeing to provide a review I was asked to help beta test. (COOL!) Now, I’m married to a QA guru. But that doesn’t mean I know what I’m doing when it comes to testing. I wasn’t being asked to sit there and try to break the program (which is a good thing, because that scares the hell out of me).

So, I wasn’t entirely surprised when at one point during the run, an error message popped up. But it wasn’t just “oops, something went wrong.” Oh, no. It was a BIG box that included a bunch of code, and the message (which I’ll paraphrase) “Please copy this and paste it into an email to address@restofaddress.”

Of course, I complied. I had no clue what the code meant or what hadn’t worked, but I did my part. And eventually, the devs and QA folks there figured out what had happened, fixed it, and thanked me (and the other five or six people to whom the same thing had happened). I’m reminded of that ad for Seven Seas salad dressing: “And I helped!”

And yes, there’s still that wonderful “final actions” list where you can choose, as I always do, “change multiple spaces to one.” (It used to say “two.” Now those weird places where there are perhaps three spaces will be magically closed up. No more having to do that one twice!)

If you used PerfectIt3, making the jump to this one is an utter no-brainer.

If you’ve been waffling, now’s the time. (Less time than it took before!)