An American Editor

March 20, 2017

The Business of Editing: The AAE Copyediting Roadmap V

I am now nearly at the point where I actually begin editing the manuscript itself. I’ve created a stylesheet and cleaned the document (see The Business of Editing: The AAE Copyediting Roadmap II), and tagged the manuscript by typecoding or applying styles (see The Business of Editing: The AAE Copyediting Roadmap III), and inserted bookmarks for callouts and other things I noticed while tagging the manuscript (see The Business of Editing: The AAE Copyediting Roadmap IV). Now it is time to create the project- or client-specific Never Spell Word dataset and then run the Never Spell macro.

Never Spell Word (NSW) lets me create project- or client-specific datasets. If I know, for example, that the client prefers “distension” to “distention,” I can, using NSW mark every instance of “distension” with green highlighting, which tells me that this is the correct spelling, and change every instance of “distention” to “distension,” which change will be made with tracking on and then highlighted in cyan to visually clue me that a change has been made (I can choose to make the changes with tracking off, but that is not something I ever do).

Tip: It is important to remember that the tab names, such as “Drugs,” in the Never Spell Manager, and in nearly all managers, can be changed to whatever name best suits your editorial business. Use the Change Tab Name button. The tab names that show when you install EditTools are placeholder names.

Highlighting is integral to EditTools. Highlighting attracts the eye and by using different highlight colors, I can, at a glance, tell whether I need to review or check something. Because of the types of books I work on, it is not unusual for Word to put a red squiggle under a word or phrase that is actually correct — it just isn’t in Word’s dictionary. Most editors would stop and check the squiggled word, but, for example, if I see it is highlighted in green, I know that it is correct and I do not have to check it — I know I have already checked the word and then added it to a tab in the Never Spell Manager.

The point is that NSW enables me to mark (via highlighting) items that are correct, items that need to be checked, items that are correct but may not be capitalized correctly, items that should never be spelled out, and items that should always be spelled out according to the stylesheet and client instructions. Some examples are shown in the image below (you can make this image, as well as other images in this essay, larger by clicking on image):

A Dataset in Notepad++

The datasets are text files. The above image shows a project-specific dataset that was opened in Notepad++ (Notepad++ is an outstanding free text editor that is a replacement for Microsoft’s Notepad). The * and $ preceding an entry indicate case sensitive and whole word only, respectively. For example (#1 in image above),

*$ms | cyan -> msec

means: find instances of “ms” as a lowercase whole word (in other words, “ms” but not, e.g., “forms” or “MS”) and change it to “msec.” What I will see in the manuscript is this:

Change Example

The cyan tells me at a glance that this has been changed by NSW. If the change is incorrect for some reason, I can reject the change, which is why I do it with tracking on.

I use NSW as a way to implement stylesheet decisions, as well as client preferences. An example is “F/M” (#2 in above image). The nice thing is that I do not need to format the entry. The Never Spell Manager, shown below, makes it easy — I just fill in the blanks, and if appropriate check one or both checkboxes, and click Add. I can easily correct an erroneous entry by double-clicking on it, correcting it, and clicking Update. And the Manager stays open and available until I click Close. With this Manager, I can make additions to any of the tabs.

The NSW Manager

I also use NSW as a way to mark things I already know are correct or incorrect and need changing so that I spend less doing spell checking tasks and more time doing higher-level editing. When I come across a new term, such as the name of a new organism, if appropriate I add it to one of the NSW datasets after I verify it so that next time it will be highlighted and, if necessary, corrected. For example, authors often type ASO3 rather than the correct AS03 (the first is the letter O then second is a zero). Having come across that mistake often, I added the instruction to change ASO3 to AS03 to my Commonly Misspelled Words dataset. Another example is the word towards. The correct spelling in American English is toward, so I added the word towards and the correction (toward) to an NSW dataset.

When I run the NSW macro, I am actually running more than what is contained in the Never Spell Words dataset — I can choose to run one, some, or all of the datasets represented by the tabs in the Never Spell Manager shown here:

Choosing Datasets

In this example, I am running all of the datasets except the Confusables dataset.

Tip: Using only the datasets that are applicable to the project allows the NSW macro to complete faster. This is especially true as your datasets grow.

I run the NSW macro over the main text; I do not run it over the reference list. My habit is to move the reference list to its own document after I style/code and do cleanup, but before I run NSW. The NSW macro requires the placement of a bookmark called “refs” at the point in the manuscript where I want the macro to stop checking text. Consequently, I do not have to move the reference list to a separate file if the list is after the material I want the macro to go over — I can just put the bookmark in the reference list head or in a line that precedes the list. I move the reference list to its own file because my next step will be to run the Journals macro, and that macro works faster and better when the reference list is in its own file, especially if the dataset is large as mine are (e.g., my AMA style dataset runs more than 212,000 entries).

As I said earlier, I keep the Never Spell Manager (shown above) open while I edit. Doing so lets me add new material to the various datasets as I edit the manuscript. The idea of the multiple tabs is to be able to have specialized datasets that are usable for all (or most) projects; for me, only the Never Spell Words dataset is project/client specific. When I come across the name of a study, for example, such as AFFIRM (Atrial Fibrillation Follow-up Investigation of Rhythm Management), I enter the information in the Studies/Trial tab dataset, because that is information that is neither project nor client specific.

I also keep open the Toggle Managers because when I come across something like the AFFIRM study I want to enter it into the appropriate Toggle dataset, too. But the Toggle macro is the subject of a later Roadmap essay (The Business of Editing: The AAE Copyediting Roadmap VIII).

After running NSW, it is time to turn attention to the reference list. The Journals macro and the Wildcard Find and Replace macro are the subjects of The Business of Editing: The AAE Copyediting Roadmap VI.

Richard Adin, An American Editor

February 15, 2016

EditTools & My Editing Process: Part II

Part I introduced the preediting steps (Steps 1 to 3). Part II discusses the remaining two preediting steps (Steps 4 and 5) and then discusses the first editing step (Step 6) in my editing process, which is editing the references.

Step 4: Moving the References

Most of the projects I work on have extensive reference lists. Sometimes a chapter will have a relatively short reference list of 50 or so, but most are at least 100 references, and sometimes are more than 1,000 references.

After the preliminary steps and before running Never Spell Word (Step 5), I move the reference list to its own file. I do this for several reasons. First, some of the macros that I use during editing can affect the references, creating undo work for me. Moving the references to their own file avoids this problem.

Second, I like to edit with Spell Check on. However, Spell Check sees many author names and foreign spellings in journal names and article titles as misspellings. That wouldn’t matter except that it often leads to the message that Spell Check can’t be used because there are too many spelling errors and so Word will turn off Spell Check — for the entire document. By moving the references to their own file, I almost always avoid that particular problem. (Yes, I am aware that I could turn off Spell Check just for the references — for example, by modifying the styles used in the references, which is what many editors do — but I like Spell Check to be on even for the references.)

Third, I want to be able to run my Journals macro unimpeded and as quickly as I can. The more material the Journals macro has to run through, the longer it takes to complete.

Fourth, I want to be able to run Wildcard Find & Replace on the references without having the macro also affect other parts of the document.

And fifth, moving the references to their own file makes it easier to check text reference callouts against the references because I can have both the primary document and the references open concurrently and on different monitors.

I do not edit the references in this step; I simply move them to their own file.

Step 5: Project-Specific Never Spell Word

The next preedit step is to create my project-specific Never Spell Word (NSW) dataset, which is shown below. Every project has its own NSW dataset (#13). The only time I use a previously created dataset is when I have edited a previous edition of the book. I assume that word usage decisions made in previous editions will continue in the current edition. This is generally reinforced when the client also sends me a copy of the stylesheet I prepared for the prior edition (or tells me to use it, knowing I have it available on my website). I do, however, go through the NSW dataset to make sure there are no changes that need to be made as a result of changes in the applicable style guide or in other pertinent guidelines (e.g., changing over-the-counter and OTC to nonprescription).

Never Spell Word dataset

Never Spell Word dataset

If I cannot use a previously created NSW dataset, I create a new one using the Never Spell Word Manager shown above. Note that when I speak of the NSW dataset, I am really speaking about the one tab in the Manager — the Never Spell Words tab (circled). Although the other tabs are part of the NSW macro, they are not project specific as I use them; however, they can be project specific, as each tab can have multiple datasets, and the tabs also can be renamed.

In the example NSW, the dataset has 70 items (#15). These items were specifically mentioned by the client or the author(s) (e.g., changing blood smear to blood film, or bone marrow to marrow) (#14), or things I noticed that will need changing (e.g., changing Acronyms and Abbreviations that appear in this chapter include: to Acronyms and Abbreviations:) (#14). As I edit and discover more items that should be added, I add them through this Manager.

The NSW macro has multiple tabs, some of which may not be relevant to the current project. Running the NSW macro brings up the NSW Selector, shown below. Here I choose which tabs to run. The default is Run All, but if I need to run only the NSW and Commonly Misspelled Words tabs for the particular project, I check those two and click OK and only those two parts of the macro will run.

Never Spell Word Selector

Never Spell Word Selector

After the NSW macro is run, it is time to begin editing.

Editing Steps

Step 6: The References

My first task is to edit the references that I moved to their own file in Step 4. I deal with the references before editing the text so I can determine whether there are “a,b,c” references (e.g., 57a, 57b) or if the references are listed alphabetically even though numbered. This is important to know for setting up the Reference # Order Check macro, found on the References menu and shown below, for tracking callout order and for renumbering if needed.

Reference # Order Check

Reference # Order Check

After I set up the Reference # Order Check macro, it is time to look at the references and see if the author followed the required style. Occasionally an author does; usually, however, the author-applied or -created style is all over the place. So the next macro I run is Wildcard Find & Replace (WFR) (shown below) and the appropriate scripts I created using WFR. The scripts focus on specific problems, such as author names and order-of-cite information (e.g., year first or last).

Wildcard Find & Replace Scripts

Wildcard Find & Replace & WFR Scripts

The scripts cure a lot of problems, but not all of them. Following the scripts, I run the Journals macro. Depending on which dataset I use, running the Journals macro may well fix nearly all of the journal names.

After running the Journals macro, I go through the references one by one, looking for remaining problems that need fixing, such as completing incomplete citations. If I come across a journal that was not in the Journals dataset, which I know because it is not color coded, I verify the journal’s name. I also go to the Journals Manager enhanced screen, shown below, so I can add the journal to multiple datasets concurrently.

Journals Manager Enhanced Screen

Journals Manager Enhanced Screen

Once I have finished editing the references, it is time to begin editing the main text (Step 7), which is the subject of Part III.

Richard Adin, An American Editor


Looking for a Deal?

You can buy EditTools in a package with PerfectIt and Editor’s Toolkit Plus 2014 at a special savings of $78 off the price if bought individually. To purchase the package at the special deal price, click Editor’s Toolkit Ultimate.

Blog at

%d bloggers like this: