{"id":19606,"date":"2022-12-24T11:57:14","date_gmt":"2022-12-24T19:57:14","guid":{"rendered":"https:\/\/www.kith.org\/jed\/?p=19606"},"modified":"2022-12-24T11:57:14","modified_gmt":"2022-12-24T19:57:14","slug":"book-review-_the-subversive-copy-editor_","status":"publish","type":"post","link":"https:\/\/www.kith.org\/jed\/2022\/12\/24\/book-review-_the-subversive-copy-editor_\/","title":{"rendered":"Book review: _The Subversive Copy Editor_"},"content":{"rendered":"\r\n<p>I just finished reading <cite>The Subversive Copy Editor<\/cite>, a book about copyediting by Carol Fisher Saller, one of the people who answer questions for the <cite>Chicago Manual of Style<\/cite> Q&A page. (Or at least she was in 2016 when this edition of this book came out.) I\u2019m not a regular reader of their Q&A, but when I\u2019ve read it I\u2019ve generally found it thoughtful and interesting. And I generally like the approach to style that <cite>Chicago<\/cite> takes.<\/p>\r\n<p>But unfortunately, I went into this book with the wrong expectations; because of the word <i>subversive<\/i> in the title, I assumed it was going to focus on how to handle political issues in copyediting. Turns out that not only is it not about that, the author several times uses phrases that I consider politically unfortunate. (One example among many: the phrase <i>tarted-up<\/i>.)<\/p>\r\n<p>She also quotes questions and answers from the <cite>Chicago<\/cite> Q&A, but many of the answers are kind of snarky and feel mildly obnoxious to me, which feels to me at odds with the core of the book.<\/p>\r\n<p>The main point of the book is described in its subtitle: \u201c(or, How to Negotiate Good Relationships with Your Writers, Your Colleagues, and Yourself).\u201d In the introduction, Saller clarifies that what she means by \u201csubversive\u201d is recommendations like:<\/p>\r\n<ul>\r\n  <li>Have a friendly relationship with your writers, not an adversarial one.<\/li>\r\n  <li>Occasionally think outside the rules; be flexible.<\/li>\r\n  <li>Help writers achieve what they want to do.<\/li>\r\n<\/ul>\r\n<p>\u2026Whereas to me (and, I think, every other editor I\u2019ve talked or worked with), those things are completely ordinary and not at all subversive.<\/p>\r\n<p>So the book ended up feeling to me mostly like an introduction to good copyediting practices for new editors, and perhaps especially for people who are new to office work of any kind. I think it\u2019s probably a pretty good introduction for such people, but there wasn\u2019t a lot in the book that I didn\u2019t already know.<\/p>\r\n<p>I was particularly surprised by the presence of a chapter focusing on things like keeping a to-do list and having a schedule and prioritizing more important work. Those are things that I\u2019m not good at, so in theory that material could have been useful to me; but it felt to me more like general advice about managing any kind of office-job workload than like something specific to copyediting.<\/p>\r\n<p>I also felt like there were some odd mismatches between some aspects of the book and others. For example, although much of the book feels to me like it\u2019s intended for beginners, Saller occasionally says things like ~\u201cWe\u2019ve all had the experience of [such-and-such thing going wrong in an office job]\u201d~ (paraphrase from memory, not exact quote), which seems to me to imply that it\u2019s not for beginners.<\/p>\r\n<p>Another example: Much of the book is about the importance of maintaining a good and friendly relationship with your writers and your editorial colleagues. But Saller includes Q&A responses that say things like \u201cIn short, your sentence is a disaster and must be rewritten for clarity.\u201d That kind of statement absolutely does not \u201clay the groundwork for an excellent author-editor relationship,\u201d which is what Saller says to do in the paragraph before she quotes that Q&A response.<\/p>\r\n<p>There are definitely things I like about this book; I mostly agree with her overall ideas and the approach she\u2019s advocating. And the book is pretty readable, and a fairly quick read.<\/p>\r\n<p>But I would say it\u2019s not primarily intended for experienced editors. And I would say that even new editors should take some aspects of it with a grain of salt.<\/p>\r\n\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[29],"tags":[],"class_list":["post-19606","post","type-post","status-publish","format-standard","hentry","category-life-updates"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/posts\/19606","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/comments?post=19606"}],"version-history":[{"count":2,"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/posts\/19606\/revisions"}],"predecessor-version":[{"id":19608,"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/posts\/19606\/revisions\/19608"}],"wp:attachment":[{"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/media?parent=19606"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/categories?post=19606"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kith.org\/jed\/wp-json\/wp\/v2\/tags?post=19606"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}