Our previous article outlined a fairly lengthy Find and Replace routine to make sure inclusive (elided) numbers follow the style outlined in the Chicago Manual. Astute reader Andrew Lockton responded with a technique that is so important, it deserves a second article. Andrew suggested taking the "Find What Expression" wildcard, which takes the form 1, 2, and so on, and putting it not in the Replace With box, where it is ordinarily used, but in the *Find What* box--something I did not know was possible. Hats off to you, Andrew.

Instructions for using the "Find What Expression" wildcard can be found here:

http://lists.topica.com/lists/editorium/read/message.html?mid=1706365638

Andrew's discovery opens up all kinds of possibilities for various problems I've previously been unable to solve, but let's look specifically at getting numbers by Chicago. The previous method required 18 separate searches. Andrew's brilliant methodology requires only three. Here's the explanation:

1. Numbers that take the form 104-105 need to be converted to 104-5:

Find What:

([1-9])0([1-9])-10([1-9])

Replace With:

102-3

What's going on there is that the first number grouping, ([1-9]), is being referred to by the 1 that follows the hyphen--in the Find What string. See it? Just before the 0 there? That tells Word to find (again) whatever was found by the first number grouping. For example, when the search hits something like "203-205," it says, "Hey, my first number group finds 2 [the first number in 203]. Let's see, is there also a 2 after the hyphen? Yes, there is!" Slicker than snake shoes, as expert word whacker Hilary Powers is fond of saying.

2. Numbers that take the form 104-110 need to be converted to 104-10:

Find What:

([1-9])0([1-9])-1([1-9])([0-9])

Replace With:

102-34

3. Numbers that take the form 111-112 or 119-120 need to be converted to 111-12 or 119-20:

Find What:

([1-9])([1-9])([0-9])-1([1-9])([0-9])

Replace With:

123-45

At first I thought it might be possible to combine 2 and 3:

([1-9])([0-9])([0-9])-1([1-9])([0-9])

But that would also find even hundreds (100, 200), which need to be ignored (100-114 rather than 100-14).

Many thanks to Andrew for the terrific tip.

_________________________________________

READERS WRITE

Alan Seiden wrote:

Here's another caps lock fixer. The program is called AntiCapsLock. It is free to try, but costs $10 to have the program remember one's settings.

http://www.orionsoft.cz/anticapslock.asp

We've set it up so that caps lock only toggles on or off when SHIFT is pressed along with the CAPS LOCK key. It works very well for a fussy computer user.

----------------------------

After reading the article "Numbers by Chicago," Jeanne Pinault wrote:

What I do with elided numbers is just replace all the hyphens with en dashes and then fix whatever comes up wrong when I edit the notes. That's because every set of endnotes I see is wrong in a slightly different way from every other set of endnotes I ever saw, so I have to read every character anyway. I can see that your marvelous find and replace would be a godsend with consistently formatted and voluminous endnotes produced on a regular basis, though. Are en dashes in there someplace?

I responded:

In the Find string, use ^150 (the en-dash code) instead of the hyphen.

----------------------------

Margaret Berson wrote:

I just was looking at your sequential replacement operation for page numbers. Why would you not use a macro that would go through and use the string position functions to evaluate the first digit of the first page number against the first digit of the second page number, deleting the unneeded first digit of the second number if it's the same, and leaving it alone if it's higher?

Wordmeister Steve Hudson sent in a macro that takes things even further. He wrote:

The following solution was designed to not just satisfy the English world with its 0-9 numerics. Use it to reduce hexadecimal addresses, Japanese, or anything. Even if the numbers aren't sequential, like hex, we just use ranges for the find such as "0-9A-F".

It is as simple as possible whilst being as generic as possible. Simpler solutions cannot work for non-English solutions as we cannot guarantee ASCII status. It is fully commented and written for clarity and education rather than speed. It will still run like greased lightning but 🙂

Public Sub NumberCruncher()
'Link this one to your toolbar
'Change any parms as needed from here
NumberCrunch ActiveDocument.Content
End Sub
Public Function NumberCrunch( _
Scope As Range, _
Optional NumberSeparator As String = "-", _
Optional Numbers As String = "0-9" _
) As String
'Another document solution from WordHeretic.com
'Produces short form number ranges anywhere in the provided
'document range. Eg 309-310 into 309-10 and 307-308 into 307-8
'You can use Unicode nnnn by using "^nnnn"
'NumberRange and architecture is for true I18N
'Known Issues: n-n will end up being n-. Eg 300-300 to 300-
'___________________
'Declare
'___________________
Const EndOfWord As String = ">"
Dim NumberRange As Range
Dim FirstNumber As Range
Dim SecondNumber As Range
Dim Separator As Range
Dim AnyNumber As String
Dim LenFirst As Long
Dim LenSecond As Long
'___________________
'Initialise
'___________________
Set NumberRange = Scope.Duplicate
Set FirstNumber = Scope.Duplicate
Set SecondNumber = Scope.Duplicate
'___________________
'Clarity
'___________________
AnyNumber = "[" & Numbers & "]@"
With NumberRange.Find
.Text = AnyNumber & NumberSeparator & AnyNumber & EndOfWord
.MatchWildcards = True
End With
'___________________
'Main program loop
'___________________
While NumberRange.Find.Execute(Replace:=wdReplaceNone)
Set Separator = NumberRange.Duplicate
With Separator.Find
.Text = NumberSeparator
.Execute(Replace:=wdReplaceNone)
End With
'So now we have the entire number range AND
'the separator range, we can calc the numbers
FirstNumber.Start = NumberRange.Start
FirstNumber.End = Separator.Start
SecondNumber.Start = Separator.End
SecondNumber.End = NumberRange.End
'Counting chars is NOT the same as an offset
LenFirst = FirstNumber.Characters.Count
LenSecond = SecondNumber.Characters.Count
'Now lets work out what's the same
'First up, if the second number is shorter than
'the first, it's already been done or is irrelevant.
'Eg 200-7
'If the second number is longer we cannot find common ground
'Eg 97-101
'Thus, we can ONLY operate on equal length numbers.
'Then, test for the number being a dynamic field
'as we can't really change those
If LenFirst = LenSecond And NumberRange.Fields.Count = 0 Then
'Now we need to match every character or finish
'We will shrink our FirstNumber range as we go,
'and delete the secondnumber range as we go
'Char comparisons DO use unicode
While FirstNumber.Characters(1) = SecondNumber.Characters(1)
FirstNumber.MoveStart
SecondNumber.Characters(1).Delete
Wend
End If
Wend
'___________________
'Destroy all objects
'___________________
Set FirstNumber = Nothing
Set SecondNumber = Nothing
Set Separator = Nothing
Set NumberRange = Nothing
End Function
Steve later added:
We may also want to include something like this if the user wants to run the macro on a range of text:
Public Sub NumberCruncherSelection()
NumberCrunch Selection.Range
End Sub

If you don't know how to use macros like that one, you can find out here:

----------------------------

The consistently brilliant Eric Fletcher wrote:

I was interested to see the tip from Meg Cox and Joy Freeman in the last Editorium posting about highlighting all instances of an item. In a job some time ago, some very foreign names were being used throughout. I knew they would cause problems later in the spell check but unless I was careful, a slightly different spelling of the same name would easily slip past. For example, "Mkandawire" might also be "Mkandewire"... I wanted to avoid the tedium of clicking the Ignore button during spell check but still have a way to check the items.

So, in order to both flag a word as already seen and turn off proofing, I created the little macro below. To use it, I select the word (or words) and click the button associated with it. All identical instances (note the MatchCase) are set in green color with no proofing. The resultant green color shows that the word has already been encountered (as noted in your reader's tip).

However, what is particularly useful about this approach is that you can then later collect all of the flagged items in a single step -- either for separate review or for use in a style guide. (This method only works for Word 10+.)

1. In the Find box, leave Find What empty but use Format to select the color (Green in my case).

2. Click the "Highlight all items found in:" box and choose Main Document. The Find button changes to Find All, and when you click it, all instances of the color green will be highlighted.

3. Now for the fun part: close the F&R dialog and choose Copy (Ctrl-C); open a new document and paste (Ctrl-V).

What you get is a list with each found item on a line of its own. You can then sort it and more easily review the list since all identical instances of the same item sort together. (...and I'm sure someone out there will even have a VBA script that could eliminate all duplicates in the sorted list!)

[Editor's note: You'll find such a script here: http://lists.topica.com/lists/editorium/read/message.html?mid=1702467672]

Here's my macro:

Sub FlagThis()
' FlagThis Macro
' Flags current selection as green with no proofing throughout the
document. E Fletcher 2003-10-23
'
Dim flagit As String
flagit = Selection
Selection.MoveLeft Unit:=wdCharacter, Count:=1
With ActiveDocument.Content.Find
.ClearFormatting
.Text = flagit
.MatchCase = True
With .Replacement
.Text = "^&"
.ClearFormatting
'-- colour and no proofing options for replace
.Font.Color = wdColorGreen
.NoProofing = True
End With
.Execute Format:=True, Replace:=wdReplaceAll
End With
Selection.MoveRight Unit:=wdWord, Count:=1
End Sub

Note that I have it set up so the cursor ends up at the end of the first word in the selection. If users want to just add color and not set the proofing off, the ".NoProofing = True" statement should be removed.

I also use a slightly modified version of this method to flag words set in a different language. My Quebec flag button sets the selection in my custom "French" character style [French (Canada) language and font color blue] so I modified the FlagThis macro to set all instances of the selection to the French style. The spell check switches languages on the fly so it checks properly in multiple languages. Then, before I print or release the final version of the file, I modify the style definition(s) to change the language color(s) to automatic.

Many thanks to Alan, Jeanne, Margaret, Steve, and Eric for their terric tips and comments.

I recently worked on a manuscript with lots of source citations, many of which had page numbers formatted like this:

122-123

I prefer the shorter style recommended in the Chicago Manual of Style (8.69):

122-23

And besides, the manuscript was inconsistent, sometimes using one style, sometimes the other. Not wanting to fix all of these by hand, I decided to put the old wildcard search to work. You can learn about searching with wildcards in my free paper "Advanced Find and Replace in Microsoft Word":

http://www.editorium.com/ftp/advancedfind.zip

The first thing I needed to do was simplify things. Consider the style for even hundreds:

100-109

100-119

100-201

In all such cases, the numbers were already in the correct style, so I decided to just get them out of the way, like this:

Find What:

00-

Replace With:

~~-

(Those tildes are just arbitrary placeholders to be turned back to zeroes later.)

With that taken care of, I originally thought I could change all the other numbers like this:

Find What:

([0-9]{3}-)[0-9]([0-9]{2})

Replace With:

12

That "Find What" string finds any set of three {3} numbers [0-9] followed by a hyphen, followed by a single number [0-9], followed by any set of two {2} numbers [0-9]. The items in parentheses are treated as as a group.

The "Replace With" string replaces the first 1 parenthetical group with itself and the second 2 parenthetical group with itself, leaving out any number [0-9] that was not grouped in parentheses.

That will definitely change 122-123 to 122-23, but it will also change 308-309 to 308-09, so we'll need to get a little fancier. How about this?

Find What:

([0-9]{3}-)[0-9]([1-9]{2})

Replace With:

12

Notice that I've changed that last number range to [1-9] rather than [0-9]. That means numbers like 308-309 will not be found but numbers like 308-319 will. (Come to think of it, that single number in the middle could probably be [1-9] as well, since there shouldn't be any page numbers like 308-019. Of course, you never know.) Now, does that solve the problem?

Well, no. We still need to deal with numbers like this:

398-415

We certainly don't want that changing to 398-15. And what about this?

247-517

Unlikely, I'll admit, but still possible.

And that means we can't do our find and replace all in one shot. Instead, we'll have to do 18 specific searches:

(1[0-9]{2}-)1([1-9][0-9])

(2[0-9]{2}-)2([1-9][0-9])

(3[0-9]{2}-)3([1-9][0-9])

(4[0-9]{2}-)4([1-9][0-9])

(5[0-9]{2}-)5([1-9][0-9])

(6[0-9]{2}-)6([1-9][0-9])

(7[0-9]{2}-)7([1-9][0-9])

(8[0-9]{2}-)8([1-9][0-9])

(9[0-9]{2}-)9([1-9][0-9])

(10[1-9]-)10([1-9])

(20[1-9]-)20([1-9])

(30[1-9]-)30([1-9])

(40[1-9]-)40([1-9])

(50[1-9]-)50([1-9])

(60[1-9]-)60([1-9])

(70[1-9]-)70([1-9])

(80[1-9]-)80([1-9])

(90[1-9]-)90([1-9])

At least that's how it looks to me. If you have a better way, I'd love to hear about it.

You can do the searches by hand if you like. You've got 20 chapters, all in separate files? Let's see--20 x 18 = 360 separate searches. Ouch! Of course, you could use my MegaReplacer program to do them all at once, freeing up your time for something more interesting:

http://www.editorium.com/14843.htm

Don't forget, we still need to turn those tildes back into zeroes:

Find What:

~~

Replace With:

00

Now all of those page numbers should be in Chicago style. How beautiful!

"What about four-digit numbers?" you ask. I leave it as an exercise for you to work out.

If you'd like this whole thing ready to run in MegaReplacer, here it is:

00-|~~-

(1[0-9]{2}-)1([1-9][0-9])|12+m

(2[0-9]{2}-)2([1-9][0-9])|12+m

(3[0-9]{2}-)3([1-9][0-9])|12+m

(4[0-9]{2}-)4([1-9][0-9])|12+m

(5[0-9]{2}-)5([1-9][0-9])|12+m

(6[0-9]{2}-)6([1-9][0-9])|12+m

(7[0-9]{2}-)7([1-9][0-9])|12+m

(8[0-9]{2}-)8([1-9][0-9])|12+m

(9[0-9]{2}-)9([1-9][0-9])|12+m

(10[1-9]-)10([1-9])|12+m

(20[1-9]-)20([1-9])|12+m

(30[1-9]-)30([1-9])|12+m

(40[1-9]-)40([1-9])|12+m

(50[1-9]-)50([1-9])|12+m

(60[1-9]-)60([1-9])|12+m

(70[1-9]-)70([1-9])|12+m

(80[1-9]-)80([1-9])|12+m

(90[1-9]-)90([1-9])|12+m

~~|00

_________________________________________

READERS WRITE

Mary Russell wrote:

I'm working on a revision of an encyclopedia on world religions that already has a 108-page word list and a 1,000-page index of terms I need to check *everything* against. I'm using your style sheet macro to slap each term I want to check into the style sheet as I go and then doing a separate pass to check them all--and having them alphabetized saves me a lot of scrolling around in those files. By the way, I *love* your macro. I run the style sheet minimized and don't even have to switch back to my original document. You should really be selling this one. I'm usually more restrained, but this really is a great idea.

--------------------------------

Meg Cox wrote:

Joy Freeman on Freelance suggested a new approach that I think will alleviate the style sheet challenge considerably. I haven't tried it yet, but I'm going to on the next chapter I start. She gave her permission to repeat the approach here:

With each occurrence of a new name, search for the same and replace it with itself in a different color (say, blue). Then you know you've already encountered it and don't need to check it against the style sheet. That way you only have to take action with variations and first occurrences. If it's blue, move on through!

I suspect this approach will come in very handy the next time I have a manuscript with hundreds of unfamiliar personal, place, and organizational names, and it will help in simpler projects as well.

Another way it will help: Sometimes in a long chapter it's hard to remember whether the full name of a person or organization has appeared yet (my clients routinely ask for full version on first occurrence in each chapter, then shortened version thereafter). If the changing to blue is done chapter by chapter (and I think it could be handled quickly--I need to think macro on this), blue will mean the full version has already occurred and an abbreviation or last-name-only may be called for. Could be useful for long sets of notes too so I know when it's time to go with a short citation! (Lately I'm seeing plenty of chapters with 70 or more notes.) Oh, and good for parenthetical citations too, so I know what I've already checked against bibliography.

[Editor's note: Our RazzmaTag program would be very useful for this kind of thing: http://www.editorium.com/razzmatag.htm.]

--------------------------------

Brad Hurley wrote:

Steve Hudson wrote:

I'd like to advise you and your readers to avoid Outlook

2003. It has more bugs than the NSW locust plague here in

Australia at the moment. I could fill an article with simple

features that cause immediate failures.

This is almost the opposite of my experience. I've been using Outlook 2003 daily on my Windows 2000 machine since last October, and it has never crashed. I have encountered several bugs and design flaws, but overall my experience has been positive. The much-improved spam filtering and the new three-pane design make it a far better program than previous versions. The upgrade from Outlook 2000 went flawlessly and it handles my large e-mail archive files (300-600 megabytes each) without a complaint. The only serious problems I've noticed so far are:

1. Editing a message in your outbox makes it impossible to send; you have to transfer it to a different folder and send it from there.

2. E-mail address auto-complete doesn't work if your contact's address book entry also has a fax number listed (this is a very frustrating flaw because Outlook should be smart enough to know you're not trying to send a fax when you've composed an e-mail message to someone).

3. Hitting the return button to start a search only works once a session; after that you have to use your mouse to click the "find now" button.

Other than that, I'm satisfied with Outlook 2003; in fact it's the only element in the Office suite that I've found worth upgrading from the 2000 versions.

Many thanks to Mary, Meg, and Brad for their helpful tips and comments.

_________________________________________

RESOURCES

Bruce Koehler wrote:

Another approach to handling accidental press of the Insert key and other keys (e.g. Caps Lock) is a small freeware program called FirstCap. It allows you to set up these potentially problematic keys in various ways such as:

* Disable

* Disable--but with a work-around to re-enable once or continuously sound an alert when pressed

Terrific little program. Just Google search on "FirstCap" for many sites that offer it.

And while I'm at it, here are a few more that would be useful to Word users:

Memokeys: "MemoKeys can help you to fill forms faster, to execute repetitive tasks without having to type every time the same text or keystrokes. The principle is simple: MemoKeys creates associations between key combinations on your keyboard and some predetermined texts or system actions . . . " Uses a Function key (F12, for example) plus an alphanumeric key. Works in all programs.

MinMax extender: adds icons by the "-" and "X" icons at the upper right of a window to allow rollup, expand window to full screen width or height (and undo), etc.

FileEx (shareware--not free): can expand most dialog boxes--a great help in Word--also allows a different default Save destination (great when you're opening a lot of files in one folder but want to save them to another location).

Many thanks to Bruce for suggesting these programs. Bruce also suggested asking newsletter readers if they know of other editing or Word-related shareware and freeware. If you do, please let us know, and we'll list them in the next newsletter: mailto:resources [at symbol] editorium.com

All this talk about editorial style sheets in the past couple of newsletters got me thinking again about lists of automatic corrections. Long ago, I wrote about this and provided a couple of such lists:

http://lists.topica.com/lists/editorium/read/message.html?mid=1708048908

http://lists.topica.com/lists/editorium/read/message.html?mid=1708127357

http://lists.topica.com/lists/editorium/read/message.html?mid=1708293844

I now realize, however, that those lists don't include nearly as many typographical errors as they could. I'm talking about errors like these:

abbout (about)

yeild (yield)

yera (year)

yoiu (you)

yoiur (your)

So here, for your editorial pleasure, is a giant list (more than 1,200 entries) compiled from various typo and AutoCorrect collections:

http://www.editorium.com/ftp/typolist.zip

The list is currently set up for use with our MegaReplacer program, with entries like this:

abbout|about+w

yeild|yield+w

yera|year+w

yoiu|you+w

yoiur|your+w

Words before the pipe symbol (|) contain the typos. Words after the pipe symbol are their replacements. And the +w at the end of each entry tells Word to search for "Whole words only." MegaReplacer will run such a list on the active document, all open documents, or all documents in a folder, fixing all of the typos in one fell swoop.

Of course, Word's spell checker will also catch these typos--if you want to click, click, click through them all manually. But why not put MegaReplacer to work while you do something more worthwhile? Of course, running that giant list on a bunch of documents could take a while, so you might want to (1) pare down the list to include only those entries you think you'll really need and (2) run it on fewer documents at a time. You can learn more about MegaReplacer here:

http://www.editorium.com/14843.htm

You might also want to use some of these entries (minus the pipe symbols and +w's) in your AutoCorrect list (some of them are probably already there). Feel free!

_

FROM WORD 2K TO 2003: WORD'S TASK PANES VBA REFERENCE

Wordmeister Steve Hudson sent his most recent article in his series about Word 2003--a sneak preview especially for Editorium Update readers before the article is published elsewhere. The article covers one of Word's most important features, the Task Pane, with an emphasis on VBA, and Steve covers the topic in almost unbelievable detail. If you want the real scoop, look no further. You can download Steve's article by clicking here:

http://www.editorium.com/ftp/taskpane.zip

Steve also wrote:

I'd like to advise you and your readers to avoid Outlook 2003. It has more bugs than the NSW locust plague here in Australia at the moment. I could fill an article with simple features that cause immediate failures.

If you are happy to live with plain text emails, you get fewer problems. Not none, fewer. Rules are broken, insofar as there are several options that crash Outlook when you select them. Contacts has a few problems that sporadically cause crashes; even picking names from your address book goes belly up regularly. 🙁 No Service Packs as of yet.

I'm putting up with it, as the rest of Office 2003 is very nice.

Many thanks to Steve for doing intense research on Office 2003 and making it available for our use.

_________________________________________

READERS WRITE

Andrew Savikas wrote:

Two quick tips came to mind while I was checking out your archives that might interest readers of your newsletter:

1. The primary motivation for most users when re-assigning the Insert key is to avoid accidental invocation of the cursed Overtype feature; adding a new function to the Insert key is just a bonus. To accomplish the former semi-permanently, just intercept the command:

Sub Overtype()
' Do nothing (or do something else)
End Sub

Then users can re-assign or un-assign the Insert key at will, without any fear of Overtype returning.

[For more information, see the past newsletters here:

http://lists.topica.com/lists/editorium/read/message.html?mid=1701260280

http://lists.topica.com/lists/editorium/read/message.html?mid=1701366500]

2. Style aliases are indispensable but can cause problems when exporting to a different format. This macro removes them (Word 2000+ for Windows):

Sub RemoveStyleAliases()
Dim sty As Style
For Each sty In ActiveDocument.Styles
sty.NameLocal = Split(sty.NameLocal, ",")(0)
Next sty
End Sub

[For more information, see the past newsletter here:

http://lists.topica.com/lists/editorium/read/message.html?mid=1703188741]

If you don't know how to use such macros, you can find out here.

--------------------------------

Meg Cox wrote:

Some editors don't like to alphabetize an editorial style sheet as they go along. For me, it's essential if the style sheet is to be usable--especially in a book with a million personal and place names, and especially if it's about an unfamiliar geographical region.

Without keeping the style sheet in alphabetical order, I'm not going to spot the close-but-not-quite situations. Case in point: in my style-sheet-nightmare project, the author was rendering the names every which way. Was it Leon Mba or Leon M'ba? With an accent on the e or not? Denis Sassou-Nguesso with or without the accent, with or without the hyphen? Sassou-Nguesso as surname only, or just Nguesso? Or Sassou Nguesso? Some names appeared infrequently enough that I never would have been able to remember whether they had come up before and how they had been rendered. (This 700-page manuscript covered politics in 14 francophone African countries over a period of 120 years.)

Even in easier projects, it's the alphabetization that enables me to spot the inconsistencies as I go along so I can change them all to the same thing. In the 14-countries project, it would have been no easy matter to go back and search and replace later because the versions of the names varied too widely, so I had to decide on the first occasion of each inconsistency. If the author wanted to go with a version different from what I had settled on, once they were all consistent I would have been able to do a global search and replace. (Thank goodness in this case cleanup was in-house!)

If I wasn't working in history and political science, this wouldn't be as much of an issue.

As it turned out, I didn't come up with a good way to do what I wanted to do. Maybe I could have with more fiddling, but I finally needed to just give up and keep moving through all the names.

Many thanks to Andrew and Meg for their helpful tips and comments.

_________________________________________

RESOURCES

The Design Science site has some marvelous advanced tutorials on Word's AutoCorrect feature:

http://www.dessci.com/en/support/tutorials/autocorrect/tutorial.htm

http://www.dessci.com/en/support/tutorials/autocorrect/advanced.htm

I get manuscripts with all kinds of weird formatting, but recently I got one from which all formatting had been removed. That might have been all right, but the note reference numbers were no longer superscript; they all looked something like this.42 I wasn't about to fix all those by hand, so I came up with this solution, which I hope you'll find as useful as I did:

1. Back up your documents, just in case.

2. Call up Word's Replace dialog (Edit > Replace).

3. In the "Find What" box, enter this (just copy and paste it from this article):

([! 0123456789,:$(])([0-9]{1,})

4. In the "Replace With" box, enter this:

12

5. Click the "More" button if it's available.

6. Put a check in the "Use wildcards" checkbox.

7. Click the "Replace All" button.

8. In the "Find What" box, enter this:

(*)

9. In the "Replace With" box, enter this (formatted as superscript):

1

10. Click the "Replace All" button.

All of your note numbers should now be in glorious superscript.

Want to know more about two-step finding and replacing?

http://lists.topica.com/lists/editorium/read/message.html?mid=1706553959

Want to know more about wildcard searching?

http://www.editorium.com/ftp/advancedfind.zip

Want to know how to remove directly applied document formatting without removing superscript, italic, bold, and so on?

http://lists.topica.com/lists/editorium/read/message.html?mid=1709845068

_________________________________________

READERS WRITE

After reading last week's newsletter with its editorial style sheet macros, Jim Pinkham wrote:

You can also overcome the limitation on having only two Word docs open to make Hilary's macro run by simply specifying the windows you wish to switch between in the macro. For example, here's a snippet from one of mine:

Selection.SelectRow

Selection.Cut

Windows("Blue Rows.doc").Activate

Selection.Paste

Windows("Weekly Improvement Analysis March 22-28.doc").Activate

When I use this macro, I'll create a new "Weekly Improvement Analysis" doc each time--so I simply edit the file name accordingly.

--------------------

Pamela Angulo wrote:

As I read today's newsletter, 2004/05/05: Editorial Style Sheet Macro, I wondered why anyone editing and creating a style sheet on a computer would be concerned about pasting copied style terms by letter or in alphabetical order. (Organizing terms by type--names, places, scientific terminology, etc.--now, that I understand.)

I copy terms to my style sheet as I go, in the order they present themselves--more or less from top to bottom of the manuscript. For some jobs (e.g., chapters by multiple authors for the same book, or individual articles for inclusion in a single magazine issue), I keep track of chapter, article, or author for each term as well. But however I handle the initial list, I sort the terms alphabetically later, *not* while I'm copying and pasting (too much time, and too much brain!).

I create different versions of the style sheet for different purposes: A single comprehensive alphabetical list for a multiple-part project allows me and the proofreader to cross-check terms across the entire project, which is always helpful; several individual alphabetical lists sorted by chapter, article, or author allow me to send only the relevant list to each author for review.

With Table > Sort in Word, arranging my style sheet in alpha order is a no-brainer, and I like that after a long day at the helm. 🙂 BTW, some people don't realize that this command will work on *any* list; the list doesn't have to be in a table.

A while back, a copyeditor posted to Freelance asking how to convert her style sheet into a table so she could sort it. It struck me *hard* then that one person's "no duh!" (it's soooo obvious) is very often another person's "no way!" (never would have thought of that).

Many thanks to Jim and Pamela for their helpful tips and observations.

_________________________________________

RESOURCES

The EServer TCLibrary of editing articles has a wealth of information on all kinds of publishing topics. Wow, look at all this great stuff!

http://tc.eserver.org/dir/Articles/Editing

Last week's newsletter provided a style sheet that editors can use to keep track of style decisions while editing in Microsoft Word. If you didn't get that style sheet, you can download it here:

http://www.editorium.com/ftp/stylesheet.zip

Hilary Powers was kind enough to provide her StyleThat macro in last week's newsletter, and this week I've adapted that macro to work with the editorial style sheet. If you select some text in a document you're editing and then run this macro, it will switch to your editorial style sheet and paste the text under the alphabetical heading where it belongs: ABCD, EFGH, and so on. See last week's newsletter for more information:

http://lists.topica.com/lists/editorium/read/message.html?mid=1716659834

And now, here's the macro:

'THE MACRO STARTS HERE
Sub StyleThat()
'Macro adapted by Hilary Powers 1/30/04; updated 4/6/04
'Adapted by Jack M. Lyon for use with editorial style sheet
If Selection.Type = wdSelectionIP Then  'No selection
GoTo HedBack
Else
FirstChar = Asc(Selection.Characters.First)
If FirstChar > 64 And FirstChar < 69 Then MySearch = "ABCD^p"
If FirstChar > 68 And FirstChar < 73 Then MySearch = "EFGH^p"
If FirstChar > 72 And FirstChar < 77 Then MySearch = "IJKL^p"
If FirstChar > 76 And FirstChar < 81 Then MySearch = "MNOP^p"
If FirstChar > 80 And FirstChar < 85 Then MySearch = "QRST^p"
If FirstChar > 84 And FirstChar < 91 Then MySearch = "UVWXYZ^p"
If FirstChar > 96 And FirstChar < 101 Then MySearch = "ABCD^p"
If FirstChar > 100 And FirstChar < 105 Then MySearch = "EFGH^p"
If FirstChar > 104 And FirstChar < 109 Then MySearch = "IJKL^p"
If FirstChar > 108 And FirstChar < 113 Then MySearch = "MNOP^p"
If FirstChar > 112 And FirstChar < 117 Then MySearch = "QRST^p"
If FirstChar > 116 And FirstChar < 123 Then MySearch = "UVWXYZ^p"
If FirstChar > 90 And FirstChar < 97 Then MySearch = "Comments:^p"
If FirstChar < 65 Or FirstChar > 122 Then MySearch = "Comments:^p"
Selection.Copy
WordBasic.NextWindow
WordBasic.StartOfDocument
Selection.Find.ClearFormatting
With Selection.Find
.Text = MySearch
.Forward = True
.Wrap = wdFindStop
.Format = False
.MatchCase = True
.MatchWholeWord = False
.MatchAllWordForms = False
.MatchSoundsLike = False
.MatchWildcards = False
End With
Selection.Find.Execute
Selection.MoveRight
Selection.Paste
Selection.TypeParagraph
GoTo Final
End If
HedBack:
WordBasic.NextWindow
Selection.MoveRight Unit:=wdCharacter, Count:=1
Final:
End Sub
'THE MACRO ENDS HERE

If you don't know how to use such macros, you can find out here.

And you can learn how to assign them to a hot key here:

http://www.topica.com/lists/editorium/read/message.html?mid=1713088939

Note that you don't have to use the macro with *my* style sheet. It will work with any document in which you've included the following headings, each followed by a carriage return:

ABCD

EFGH

IJKL

MNOP

QRST

UVWXYZ

Comments:

_________________________________________

READERS WRITE

Last week, expert word whacker Hilary Powers sent her StyleThat macro, which I proceeded to gum up. The problem was, it didn't want to work correctly in Word 2000; possibly some of the commands are specific to Word 2003. At any rate, here is Hilary's macro in its pristine state, and many thanks to her for providing it.

Hilary wrote, "The macro relies on having two [and only two] files open at a time. The truly charming thing is that you can use one hot key for both chores: putting something on the style sheet and also priming the style sheet for its next use and returning to the main document.

'THE MACRO STARTS HERE
Sub StyleThat()
' Macro adapted by Hilary Powers 1/30/04; updated 4/6/04
If Selection.Type = wdSelectionIP Then
GoTo HedBack
Else
Selection.Copy
WordBasic.NextWindow
Selection.PasteAndFormat (wdPasteDefault)
GoTo Final
End If
HedBack:
Selection.TypeParagraph
WordBasic.NextWindow
Selection.MoveRight Unit:=wdCharacter, Count:=1
Final:
End Sub
'THE MACRO ENDS HERE

If you don't know how to use such macros, you can find out here.

And you can learn how to assign them to a hot key here:

http://www.topica.com/lists/editorium/read/message.html?mid=1713088939

_________________________________________

RESOURCES

I've been fighting the battle against spam (junk email) but not very effectively, even though I've tried a couple of top-notch spam-fighting programs. Then this week I decided to try SpamArrest, and I'm thrilled to say it's actually won the war. Boy, has my inbox been quiet.

When people send me an email message, they receive an email message in return that asks them to click a link to register themselves (a one-time operation) as someone who can send me messages. Spammers, of course, won't bother to do this, which basically means no more spam. It's easy to preregister family, friends, associates, and email newsletters to which I subscribe. The completely online program (no software involved) gives me complete control over how spam is handled, and it's very easy to use.

If you'd like to know more, click here:

http://spamarrest.com/affl?1403707

And if you decide to sign up, please do so through the link above. Since I'm now a SpamArrest affiliate, your support will help keep Editorium Update alive and kicking. Thanks!

Boilerplate is text you can use over and over again as needed. For example, the Fine Print section of this newsletter is boilerplate. Here's a little-known but useful way to create boilerplate in Microsoft Word:

1. Create a new document to hold all of your boilerplate text.

2. Paste your boilerplate text into it (obviously enough).

3. Select each chunk of boilerplate text and apply a bookmark to it (Insert > Bookmark). Make the bookmark names short and easy to remember. You may even want to keep a list of the bookmarks for reference. (You'll see why in just a minute.)

4. Save your document with a name like "Boilerplate" in an easy-to-find folder.

Now, when you're working on some document and want to insert some boilerplate text, here's what to do:

1. Click Insert > File.

2. Navigate to your Boilerplate file and click it.

3. Click the "Range" button.

4. Enter the name of the bookmark for the chunk of boilerplate you want to use. Unfortunately, Word won't give you a dropdown list of the bookmarks, which is why you should use short, memorable bookmark names and keep a list of what they are.

5. Click the "Insert" button.

The boilerplate for the bookmark you entered will be inserted into your document.

_________________________________________

READERS WRITE

Answering the question "How many pages per hour should someone be able to edit on-screen?" expert word-whacker Hilary Powers wrote:

"Should" is a hard word to apply, as the work varies so much according to the condition of the manuscript and the skills of the editor. But one thing I can say: pages-per-hour production should not be lower than the equivalent paper speed.

For the purposes of pricing, paper speed expectations remain the standard, much as 250 words remains the standard page decades after the demise of the 10-pitch typewriter.

For doing the work, I find that I'm reliably between 150% and 300% of the paper speed expectations--but I've been counting keystrokes and squeezing electrons till they scream for ten years now. It'd be a very reasonable first goal to try to match paper speed on-screen--without rushing. Rather, look for ways to get the effects you want as easily as possible . . . and keep looking after you get back to your paper level, as by that point you'll probably have no more than scratched the surface of what's possible.

A job I finished a bit ago--a near-300-page manuscript in very good shape, well written and with a charming subject--had a net thruput of 14.5 pages per hour. That's close to the top I've achieved thus far for straight editing, but not the absolute max if memory serves.

------------------------

Hilary also wrote:

Here's another wrinkle on the title-case macro:

Sub SentenceTitle()
' Macro written 3/20/2004 by Hilary Powers
Selection.Range.Case = wdLowerCase
Selection.MoveLeft Unit:=wdCharacter, Count:=1
Selection.Find.ClearFormatting
With Selection.Find
.text = ":"
End With
Selection.Find.Execute
Selection.MoveRight Unit:=wdCharacter, Count:=2
Selection.Range.Case = wdNextCase
End Sub

It's for converting two-part title-case titles to sentence case: Select everything but the first word and hit the hot key, and it all goes lowercase except the word following the colon. . . . A godsend for a 50-page reference list with mixed formatting that needs to go to APA. (A refined version would let you select the whole title and then uppercase both the first word and the word after the colon, but I got lazy.)

If you don't know how to use macros like that one, you can find out here:

Many thanks to Hilary for her terrific tips.

_________________________________________

RESOURCES

Where does the term "boilerplate" come from? You can find out at World Wide Words and The Word Detective, both wonderful sites for those interested in words:

http://www.quinion.com/words/index.php

http://www.word-detective.com/index.html