Log In

Home
    - Create Journal
    - Update
    - Download

LiveJournal
    - News
    - Paid Accounts
    - Contributors

Customize
    - Customize Journal
    - Create Style
    - Edit Style

Find Users
    - Random!
    - By Region
    - By Interest
    - Search

Edit ...
    - Personal Info &
      Settings
    - Your Friends
    - Old Entries
    - Your Pictures
    - Your Password

Developer Area

Need Help?
    - Lost Password?
    - Freq. Asked
      Questions
    - Support Area



Full o' Doom ([info]doomsday) wrote in [info]otf_wank,
@ 2009-06-01 17:52:00


Previous Entry  Add to memories!  Tell a Friend!  Next Entry
The, you fucking shithead. The.
This is a short and sweet one-man show, but it packs quite a wallop.

David Mack, the author of several Star Trek novelizations and other assorted works, is displeased with the copyediting of his current book. According to him, the editor was much too heavy-handed, essentially rewriting his material. So he calmly informed his publisher and they sorted everything out in a manner that left all parties involved satisfied.

Oh wait, I mean he posted a threatening rant on his public journal. I always mix those two up!

Die, Stupid Copy Editor, Die!
31 May 2009 in Personal | No comments

Some stupid (and luckily for him/her, anonymous) copy editor apparently took it upon him/herself to almost completely rewrite the manuscript for my latest novel, Star Trek Vanguard: Precipice. I learned this when I was handed a stack of pages slathered in so much red ink that I thought it had been left at the scene of an ax murder.

This idiot copy editor is going to wind up wasting a week of my time, because that’s how long it’s going to take me to go through the novel page by page with an eraser, undoing the damage this motherfucker has wrought upon my prose.

Jackass copyeditor who did this, whoever you are, if you read this, don’t ever fucking touch one of my books again. And pray to whatever god you believe in that I never find out who you are or where you live.

Die, you fucking shithead. Die.

Shockingly, David received some private negative feedback about this post and deleted it. But don't worry—the one he replaced it with is longer, whinier, and just as entertaining.

Note to Would-Be Commenters
1 June 2009 in Personal

For those of you who might not yet have noticed, I moderate all comments here on my official blog. In practice, that means if you come in here looking for a fight, I can simply decide not to let your comments see the light of day.

To those of you who felt as if it were your right to go all high and mighty on me because I needed to vent after seeing what an overzealous copy editor did to my latest mauscript, spare me your indignation and your insults.

The ms. went to production with a cover sheet from my line editor that specifically requested a “light” copy edit with queries. My editor is the one who gave me the erasers to fix this mess.

What came back was a wholesale rewrite, including arbitrary changes of sentences, deletion of sentences and paragraphs, recasting of sentences, and a host of other intrusive changes that, in the world of professional publishing, are outside the purview of a copy editor. Those privileges are reserved for a book’s line editor (i.e., the editor who acquired the book and works directly with me).

I have been writing books professionally for 10 years. I know the difference between a proper, light copy edit and a heavy-handed writer wannabe who imagines he or she can write my book better than I can. I do not object to the many sensible notations that most copy editors make, or the myriad small errors they help me fix. I do, however, object when one of them takes it upon him/herself to second-guess my creative choices.

Contrary to popular belief, even in this modern digital age, much of the book publishing industry still operates on hard copy with handwritten notations. It’s an industry in which traditions die hard. That is why I have the original ms. on my dining-room table, marked up in red pencil; that is also why I have a pair of erasers that I am using to undo invasive and uncalled-for changes.

To the person who thought they were being impossibly clever by pointing out typos in my Twitter comment about this mess, it might behoove you to keep in mind that Twitter is an informal medium. Also, in Internet-gamer parlance, such typos — particularly “teh,” which was done deliberately — are often intentional and used to convey both intense feeling and humorous intent.

The reason I can’t simply write “STET” on the ms. is that, in my experience, doing so is rarely sufficient to prevent the unwanted edits from being carried forward by production. The only real insurance against the propagation of unwanted changes is literally to erase them from the ms.

Lastly, to all of you who deigned to lecture me that because I choose to use my personal forum to vent my rage rather than scream out my window and create a public disturbance that would bring the local constabulary to my door, and to all of you who therefore concluded that I must not be much of a writer, I would just like to point out that you are confusing two unrelated issues. The manner in which one vents in anger bears little relation to how one composes prose in a calm state of mind. To evaluate a writer’s oeuvre based on such an offering would be tantamount to judging all of Hemingway’s or Brautigan’s respective works based on their suicide notes.


(Read comments) - (Post a new comment)

In case you were wondering what it looks like...
[info]issendai
2009-06-02 04:29 am UTC (link)
*groan*

For the record, I've only copyedited technical writers and copywriters, and it usually goes like this:

Me: Here, have a page covered in red.

Them: Thanks. Here, have back a new version where we made the changes we liked.

Me: Here, have some fine-tuning.

Them: Here, have back a page that's completely fixed except for one typo that we inserted specially for this round.

Me: LOL typo. Here, have a nice perfect page.

Production: We took a crack at it. How's it look?

Me: Like you were on crack.

Production: How about now?

Me: Crack's wearing off.

Production: How about now?

Me: Almost poifect.

Production: Can we insert a typo?

Me: LOL typo. No.

Production: Aww.

Printer: We took a crack at it. How does it look?

[Choose one:]

-----

A.

Me: Lovely! Smack it on the ass and send it home to Mamma.

-----

B.

Me: AAAAUGH WTF HOW DID YOU ERASE ONLY THE CAPITAL I'S FROM ALL OF THE SUBHEADINGS

Production: LOL technical difficulties. How is it now?

Me: Peachy!

-----

...and at this point it vanishes into the ether, to arrive several months later as hardbound copies riddled with errors that several layers of editors, copyeditors, proofreaders, checkers, and production people totally missed. We are professionals, dammit, and we have industry-wide standards to uphold.

So yeah. Become a diva, pay asshole tax for as long as you can stay employed in the business. I gather it's different in fiction, but see... that's why I'm over here in technical writing with the sane people.

(Reply to this)(Thread)

Re: In case you were wondering what it looks like...
[info]issendai
2009-06-02 04:37 am UTC (link)
ETA: Having read his second post, I've got to add that his comments about line editing vs. a light copyedit are correct, and so are his comments about having to erase edits so they don't get carried forward. People ignore stet requests ALL THE FUCKING TIME. It's one of the top errors for the second round of production editing--you tell them to ignore an edit, and they either can't work out which edit it applies to (common when edits are thick) or can't tell that there's a stet comment at all (again, common when edits are thick) or have the brains of marmosets on Mad Dog 20/20 (regrettably common when editors are thick), and the edit gets made anyway. And the editor wears another fraction of a millimeter off the enamel of their molars.

That said, he's still being a dick.

(Reply to this)(Parent)(Thread)

Re: In case you were wondering what it looks like...
[info]pandonkey
2009-06-02 05:00 am UTC (link)
In response to this and your previous post: dead-on account of the editing process; yes, good point, even a big red "STET ALL" gets ignored half the time; and yep, pretty much still a dick.

(Reply to this)(Parent)

Re: In case you were wondering what it looks like...
[info]bobafeis
2009-06-02 05:19 am UTC (link)
Another yes to everything you said. And for the record, fiction gets pretty much the same treatment, only there is a lot more arguing over what's a necessary edit, and whether the deathless prose is more important than readability.

(An editor I worked with once put a giant red "STET ALL" on every single page of a ms. It came back with some pages still in the original, some pages completely revised, and some pages half revised. There was a lot of yelling and screaming and throwing stuff that day.)

I'd have sympathy for him if he weren't being such a dick, but yeah, he's a dick.

(Reply to this)(Parent)

Re: In case you were wondering what it looks like...
[info]white_serpent
2009-06-02 05:20 am UTC (link)
Yeah, the second post put things into perspective... except for the whole "And pray to whatever god you believe in that I never find out who you are or where you live" bit.

(Reply to this)(Parent)(Thread)

Re: In case you were wondering what it looks like...
[info]issendai
2009-06-02 06:20 am UTC (link)
Yes, there was a moment there when the shark wondered why that person on a motorcycle was leaping over its tank.

(Reply to this)(Parent)

Re: In case you were wondering what it looks like...
[info]esorlehcar
2009-06-02 07:05 am UTC (link)
I gather it's different in fiction, but see... that's why I'm over here in technical writing with the sane people.

I edit technical writing as well, and... well. It never would have occurred to me to refer to my authors as "sane." Well, no, that's not true--many of them lovely, sane people who understand an editor's job and are happy to work with us. But many of them are really, really not.

I've never dealt with anyone anywhere near as insane as this guy, but just last week I got a two-page screaming e-mail (and by screaming, I mean entirely in caps) about how we had destroyed this author's entire work and it was unreadable and he couldn't believe we would sign off on something that was so amateurish and sub-par. When I expressed bafflement at this diatribe, it quickly became evident that he was looking at his original input, not the edited copy. In other words, his two pages of screaming about unprofessional, amateurish work? Referred directly to his own writing.

(Reply to this)(Parent)(Thread)

Re: In case you were wondering what it looks like...
[info]kookaburra
2009-06-02 09:59 am UTC (link)
I just let out the loudest, donkeyish bray of laughter at that. Heeee.

I think I find it so funny because, minus the sending a yell-y email, it's something I could see myself doing

(Reply to this)(Parent)

Re: In case you were wondering what it looks like...
[info]white_tean
2009-06-05 04:03 pm UTC (link)
Oh my golly-gumdrops, that is HILARIOUS.
Did he write his work in a fugue state so he couldn't even recognise its flaws at the time? WTH?

The mind boggles. That's just... so, so, hilarious.

(Reply to this)(Parent)

Re: In case you were wondering what it looks like...
[info]damien
2009-06-02 10:06 am UTC (link)
Hah.

I copy/edit technical documents on nuclear powerplants and so far, my responsibilities consist of doing one run-through set of English edits, and then sending the document off into the ether.

Suddenly, I feel so much better about the fact that my eyes tend to cross whenever someone mentions aluminum.

(Reply to this)(Parent)

Re: In case you were wondering what it looks like...
[info]oliphauntine
2009-06-02 06:48 pm UTC (link)
*is production editor; kicks her typesetter's arse if they ignore corrections.*

It does sound like an overenthusiastic copy-editor but, if he was an author of mine and kicking off like that at one of my freelancers, he'd be getting short shrift. Tosser.

(Reply to this)(Parent)


(Read comments) -

 
   
Privacy Policy - COPPA
Legal Disclaimer - Site Map