In The Business of Editing: The AAE Copyediting Roadmap IX, I discussed the Enhanced Search, Count, and Replace (SCR) macro and how I use it while editing manuscript. This essay deals with inserting queries/comments into the manuscript during editing.
When I first began freelancing, a client (an in-house production editor) told me that as important as good editing skills are, even more important is how authors are queried. The reason, the editor said, is that when I speak to the author, I am speaking on behalf of the client. Of course, that got me thinking about comments and led me to the realization that comments are not only important as alerts to clients and authors about potential problems, but as a marketing tool for me. I wish I could say that I never let frustration with a manuscript or a client appear in comments I have inserted, but I can say that when the frustration appeared, I had made a conscious decision to let it appear.
Querying the author or the in-house editor or the compositor is usually done in one of two ways: (a) inserting the comment inline in the text or (b) inserting the comment as balloon text such as is done using Word’s Comment feature. Because time is money in my editorial business, I rely on EditTools’ Insert Query and Comment Editor macros to insert queries. (For this essay, “queries” and “comments” are used interchangeably and the one includes the other. The oft-stated distinction between the two terms is that a query asks a question whereas a comment makes a statement [e.g., “AQ: Is it OK/correct that I changed 1 to 2 to conform with the previous quantity?” is a query, whereas “Ed/COMP: This needs to be set in sans serif.” is a comment].) Insert Query lets you choose between inserting the comment as a Word comment (balloon text) or inline, as shown here (you can make an image in this essay larger by clicking on the image):
I have repeatedly said that time is money when editing. My goal is to minimize the time I need to spend doing “routine” tasks and maximize the time I have available for actual editing. Prior to Insert Query, I had to keyboard every query, even if it was the same query, perhaps with some modification, as inserted a dozen times before in the manuscript. Keyboarding slowed me down considerably. Although I have become a fairly decent typist over the years, I still am neither a fast typist nor one with 100% accuracy. So, keyboarding a query longer than a few words took (takes) time — time for the original keyboarding and time to review that keyboarding and time to correct the errors in my keyboarding.
Using keyboard shortcuts sped up the process but was limited for many reasons. After a while it became difficult to remember all of my keyboard shortcuts — I had them for everything, not just for queries — and there was a limit to how many quickly accessible keyboard shortcuts I could create. I eventually kept a list of my keyboard shortcuts, but that wasn’t a panacea because as the list grew, I had to take the time to look up the shortcut. Also complicating the situation was when I needed to modify a query: the original query was written for Jones on Capitalistic Medicine and now needs to be modified for Smith on Mercy Medicine. These and other limitations and problems led to the Insert Query macro.
As the image below shows, using Insert Query I am able to store a large number of “standard” queries (#A in image; the count shows the number of saved queries for the Reference Queries tab [#1] only) and access them as I need them. To make it easier and quicker to access a query, I separate the queries into categories (#2) that I create. After selecting the category, I select the query (#3) I want to insert. The selected query appears in the “insert” windows (#4), where I can modify the query if necessary. In this example, there are three underscores that need to be replaced with the relevant information. It is in this field (#4) that I make the change, after which I click Insert to have the query inserted in the text as a balloon comment.
One of the tabs is a project-specific tab (#5 in the image below; all of the tabs work the same, so you can not only rename any of the tabs, but you can have multiple project-specific tabs). As is shown at #B, this tab has 104 available project-specific queries from which I can choose. What I do is copy a query that I need for a project from one of the other tabs and add it (clicking Add to add it to the dataset rather than Insert to add it to the document) to the project-specific dataset. When I am done with a project, I copy those queries that I specially created for the project and that did not come from another tab that I think will be usable for other projects to one of the other tabs.
Take a look at the query shown in the above image (#6). How many times would you like to type it? Once was enough for me. Yet look at the query. The query packs a lot of information and shows that I did my job. It tells both the client and the author that I am competent and knowledgeable. Most importantly, as several clients have commented on seeing this and similar queries, it tells the author that the client has selected a professional editor and that the client cares about the author’s book; it gives the author confidence in the quality of the editing and competency of the editor; and it confirms to the client that a wise choice was made when I was selected to edit the book. In other words, it acts as a marketing tool.
It is easy to “perfect” a query when you only have to think of it once and only have to keyboard it once. In addition, it is easy, with a tool like Insert Query, to maintain a library of queries. Because I can create as many categories as I want (#7), I can organize the queries into logical groups that make finding the right query quick.
I use Insert Query to insert every comment that gets inserted in a manuscript. Even if I do not have the exact query I want in a dataset, I have found that using Insert Query to modify an existing comment or to create a new comment works best for me. Using Insert Query gives me the opportunity to add the revised or new query to my dataset without having to enter it twice.
Remember that the idea is to create the wheel once and reuse it, not recreate it each time. Comments can be time-consuming. Insert Query saves me time, thus making me more profitable; even a savings of just a few seconds per query can add up over time to a significant increase in profit. Additionally, Insert Query reduces the number of embarrassing typing mistakes that are made, thereby making me look more professional.
Sometimes a comment needs to be modified, deleted, or reviewed. The Business of Editing: The AAE Copyediting Roadmap XI discusses how I use Comment Editor when I need to access an already inserted comment.
Richard Adin, An American Editor
The Business of Editing: The AAE Copyediting Roadmap XI
Tags: AAE approach to editing, Comment Editor, copyediting roadmap, editing comments and queries, guide to copyediting, Insert Query, inserting comments and queries, methodology
In The Business of Editing: The AAE Copyediting Roadmap X, I discussed how I use Insert Query to insert a query or comment into the manuscript. Sometimes an inserted query needs to be modified or deleted or just reviewed. With Microsoft’s system, you need to find that inserted comment and go to it. Most of the time I do not want to leave my current editing location, but Microsoft doesn’t let me stay. Consequently, I use EditTools’ Comment Editor to deal with already-inserted comments.
Comment Editor, shown below (you can make an image in this essay larger by clicking on the image), lets me either move to the comment and then return to where I was in the manuscript (#1 and #2 in image; if I check the boxes in #1, I will automatically be taken to and returned from a selected comment every time I select one, whereas #2 lets me make the leap only when I click the buttons; I prefer to use method #2) or deal with the comment without moving from my current location. In addition, it gives me the ability to find the comment I want to modify (or delete) without having to go through each comment (#3). This is particularly useful in a chapter with a lot of comments (in the example shown in the image, the chapter has 54 comments).
The Comment Editor dialog
Comment Editor shows all of the comments I have inserted in the manuscript using either Insert Query, which was discussed in The Business of Editing: The AAE Copyediting Roadmap X, or Microsoft’s method. In other words, Comment Editor does not require using Insert Query. Comment Editor also displays comments that were inserted by either the authors or other editors before I was given the manuscript. It is not necessary for a comment to be inserted using Insert Query for it to appear in Comment Editor; it just has to be a properly inserted comment.
Comment Editor lets me use the scrollbar (#4 in image below) to scroll through the comments until I find the one I want. When I find the comment I want to review, edit, or delete, I select it (#5). The complete text of a selected comment appears in the text box (#6).
Selecting a query for editing
With the selected comment text in the text box, I can edit the comment, as shown here:
Editing the selected query
The highlighted text in the above image identifies the change I made. (The highlighting is just to show the modification I made; you cannot highlight the comment text. Although Comment Editor makes editing of comments easier, it is still limited by what actions Microsoft will allow.) Clicking Update (#7) modifies the comment in the document. If I want to delete the comment, I click Delete (#8). I generally do not keep Comment Editor open as I work as I do not often have to edit or delete a comment. But when I do keep it open, I click the Refresh button (#9 in the above image) to refresh the list of comments displayed (#10). Refreshing will show the comments that remain in the manuscript and their renumbering. In other words, had I deleted rather than modified the selected comment, then the comment immediately following it would have become FES25. Refreshing would show that change without requiring closing and reopening Comment Editor.
Microsoft imposes limits on the length (i.e., number of characters including spaces) a comment can be (#11 in the above image). I admit that it is rare that I would write a comment that comes close to that limit, but there have been a couple of times in my editing career when I have come close to that limit. Sometimes a lengthy explanation is needed. Remember that we are talking about characters with spaces, not words. To give you an idea of the difference, the preceding paragraph (“The highlighted text…and reopening Comment Editor.”) is 160 words but 943 characters. The maximum size a comment can be is 2000 characters; Comment Editor keeps me posted on the length of a comment (#11).
A good example of the utility of Comment Editor is shown in the next image. While editing the chapter from which these examples are drawn, I came across the initialism ITP, which can substitute for several diseases. Based on context, I replaced ITP with immune thrombocytopenia (ITP); however, the author could have meant idiopathic thrombocytopenic purpura. Consequently, I inserted the comment shown.
An example
Note that it is the third comment in the chapter. Suppose the author defined ITP much later in the chapter as idiopathic thrombocytopenic purpura. That means I erred in my expansion of ITP earlier. Of course, there are several ways to locate the earlier expansion of ITP, including using Bookmarks (see The Business of Editing: The AAE Copyediting Roadmap IV for how bookmarks can be used), but what I really need to know is whether I misdefined ITP and did I query it. I can check Comment Editor and when I find comment numbered FES3, I can move to it, correct the expansion, run the Enhanced Search, Count, and Replace macro (see The Business of Editing: The AAE Copyediting Roadmap IX for a discussion of this macro), return to where I was in the manuscript when I discovered the error, and either delete or modify the comment.
Although not necessary, I view Insert Query and Comment Editor as complementary — a united pair of macros; that is, I insert all comments using Insert Query and I edit all comments using Comment Editor. Comment Editor is an easy way to navigate and modify comments. Combined with Insert Query, it minimizes the amount of time needed to locate and deal with comments. The quicker and more efficiently I can deal with comments, the more profit I make.
Do you have a more efficient method for editing comments and queries?
Richard Adin, An American Editor
Share this:
Like this: