I've occasionally mentioned this in passing, but based on recent questions from readers, it seems worth making a fuss about: Yes, you *can* use a carriage return in a wildcard search.

People who use Microsoft Word often get stymied by this. They try doing a wildcard search with a string like this one:

^pSee(*)^p

What do they get? An error message: "^p is not a valid special character for the Find What box or is not supported when the Use Wildcards check box is selected."

Then they give up: "Dang! Guess I can't look for carriage returns in a wildcard search." In the immortal words of Winston Churchill, "Never, never, never give up." There's almost always a solution if you'll just hang in there and look for it. In this case, the solution is to use the ASCII character code for a carriage return. That code is:

^013

So our theoretical wildcard search would look like this:

^013See(*)^013

And that will work--unless you're using a Macintosh. On a Mac, Word simply won't find anything or (as just happened to me when I was testing this) your computer will lock up. But, surprisingly, there is a solution, which took a considerable amount of messing around to figure out. Use the ^013 but "escape" it with a backslash and treat it as a range with square brackets. In other words, use this:

[^013]

If you're a Mac user, you know what a breakthrough that is.

Finally, a caution: If you're *replacing* with carriage returns, don't use the ASCII code. Instead, use the good old paragraph code, ^p. Why? Because ^013 and ^p are not the same thing. ^p is a Word carriage return, and as such it holds formatting information that ^013 doesn't. If you replace with ^013, that formatting may be lost.

Want to know more about wildcard searching? See David Varner's comment and my response in today's Readers Write column.

_________________________________________

READERS WRITE

David Varner wrote:

"I wanted to bring up your mention of wildcard searching as a skill. You said it 'may be the most important tool you can acquire.' Okay, I've read all your articles and tried the different tips. Heck, I've printed out all the articles. But it's not the same as having one dedicated wildcard text source. And so the question is, any chance you can point me to (or create/compile) a clear and straightforward, whole enchilada wildcard search and replace manual? Or maybe I could just cut and paste all your wildcard Editorium Updates together!"

I responded to David that I'd already done this, in a document named "Advanced Find and Replace in Microsoft Word." I sent the document to him, and I'm making it available as a free download for anyone else who wants it. This document is worth your time, believe me. You can start the download by clicking here:

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

I'd like to thank Bob Janes for formatting and editing the document and especially for compiling the reference section at the end.

___________________________

After reading my philosophical ramblings on the value of technical literacy in last week's newsletter, Dan A. Wilson sent this terrific comment. Thanks, Dan!

"In business talks and seminars aimed at corporate climbers and white-collar execs in the past several years, I've begun including this phrase at opportune times:

"'Time was, and not too long ago, that the value of an individual to an organization increased geometrically when he or she became computer-literate. Today, literacy at the computer no longer pulls much weight: you have to be computer-sophisticated today, and that means simply that you must have come to regard the computer as far and away your most valuable tool, your ultimate enabler, your brain's second-in command. A brain with a pencil in its hand cannot compete--indeed cannot even credibly challenge--a brain with a computer and computer-sophistication at its disposal. Regarding the machine as an enemy, an obstacle, an unnecessary complication is lethal, and the individual who has that view of the computer is at least dying, if not already dead, in the world of business affairs, but probably doesn't yet know it.'"

___________________________

In the February 26 newsletter, I asked readers to send in their hyphenation exception dictionaries to share with the rest of the world. Rebecca Evans (evansreb@earthlink.net) actually did! Thanks, Rebecca! The dictionary is available for download here:

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

Here are Rebecca's comments on the dictionary:

"This is the hyphenation exception dictionary I currently use with Ventura. Ventura lets me specify how many letters must appear before a hyphen at the beginning of a word and how many after at the end so some of the words show hyphenation points at places I would not actually allow.

"In Ventura, words in the exception dictionary shown without hyphenation points are words that Ventura is told not to hyphenate at all. I use this for words that hyphenate differently depending on usage, such as pro-ject and proj-ect. I also place unhyphenated words in here to prevent unfortunate breaks, such as anal-ist.

"The words in this exception list also don't include every possible hyphenation point because I use this list to force preferred hyphenation, such as dem-onstrate instead of demon-strate.

"Microsoft Word and Ventura mis-hyphenate differently, I would imagine, so many of these words may hyphenate properly in Word. In fact, I've been using this list for so long now (so many versions of Ventura) that many of these may actually hyphenate properly in Ventura."

___________________________

Hilary Powers sent in a terrific macro for working with serial commas. Thanks, Hilary! Here are her comments, followed by the macro:

"Remember I asked awhile back about automating the placement of serial commas? This doesn't do the whole job, but it takes a lot of the curse off of the problem of dealing with an AP author who's writing for a Chicago publisher.

"It goes to the next instance of the word 'and,' backs up a space, and puts in a comma--ignoring 'And' and 'andiron' and the like. (I may do a partner for 'or' one day, but that doesn't come up nearly as often.)

"I have it assigned to the hot key Alt-/ and to a voice macro pronounced 'seer-comm.' So when I'm reading along and I see a spot that needs a serial comma coming up, I just say or key the command and the comma appears where it belongs, without the need to mouse to the exact spot. And if there was another 'and' in the way that I missed seeing, well, that's what Ctrl-Z is for."

'THE MACRO STARTS HERE
'Serial Macro
'Macro written 02/27/03 by Hilary Powers
'
Selection.Find.ClearFormatting
With Selection.Find
.text = " and"
.MatchCase = True
.MatchWholeWord = True
End With
Selection.Find.Execute
Selection.MoveLeft Unit:=wdCharacter, Count:=1
Selection.TypeText text:=","
'THE MACRO ENDS HERE

If you don't know how to use macros like that one, you can learn how here.

_________________________________________

RESOURCES

Steve Hudson is making his consulting and training services and Microsoft Word spellbooks and macro packages available at his new Web site, here:

http://www.geocities.com/word_heretic/products.html

Check it out! A great way to improve your technical literacy.

I work with lots of authors who use WordPerfect. Sometimes they pass their documents on to colleagues who use Microsoft Word. That wouldn't be a problem if the authors would first save their documents in Word format. But they don't, and their colleagues work on the documents in Word, pass them around to others, and then give them back to the authors, who send them to me.

When I open these documents they look okay--except that some of the characters look kind of funny. The quotation marks and apostrophes are a little crooked, and the em dashes are thick and bold. What's going on here?

What's going on is that these aren't regular ANSI characters. You can prove this by selecting one and then pressing CTRL + SPACEBAR to remove any directly applied formatting. When you do, the character will turn into some other character. With this particular kind of weirdness, an opening quotation mark (for example) will become a capital A. You could Find and Replace these with real quotation marks, but your document may have hundreds--even thousands--of *real* capital A's that you want to preserve.

Here's a list of the pseudo-characters (the ones I've identified; there could be more) and their corresponding true identities:

CHARACTER DISGUISED AS TRUE IDENTITY (sort of)

Em dash C

En dash B

Opening quotation mark A

Closing quotation mark @

Opening single quotation mark >

Closing single quotation mark

(apostrophe) =

Another way to prove something weird is happening is to put your cursor in front of one of these characters and then run the macro you'll find here:

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

The macro will tell you that the ANSI number is 40--which is really the number for an opening parenthesis. That will be true whether you're checking a pseudo-quotation mark, em dash, en dash, whatever. So you can't Find and Replace them by using character number 40, either, since your document may contain legitimate parentheses.

What's needed is a way to Find and Replace a character that is an A (or whatever) *and* has the ANSI number 40. At the end of this article is a macro (one for Word 97 and above; one for Word 6 and 95) that will do just that, for all the weird characters in question.

Now, if you run into this WordPerfect weirdness, you'll have a way to fix it. If you know about other characters that act the same way, please let me know and I'll include them in a future newsletter with a revised macro.

If you remove directly applied formatting and the character (such as an em dash) *doesn't* change to something else (such as a C) but instead to a less-bold version of the same thing (which can happen), then the macro won't fix it. It if you know what's going on with *these* weird characters and how to fix them, please let me know and I'll share your solution in the newsletter.

If you don't know how to use macros like the following, you can learn how here.

'MACRO FOR WORD 97 AND ABOVE STARTS HERE

Dim a

Dim i

Dim FalseChar$

Dim TrueChar$

Dim ThisChar

WordBasic.EditFindClearFormatting

WordBasic.EditReplaceClearFormatting

WordBasic.StartOfDocument

'Check for platform

a = InStr(WordBasic.[AppInfo$](1), "Macintosh")

For i = 1 To 6

'Set find and replace variables

Select Case i

Case 1

FalseChar$ = "C"

If a Then

TrueChar$ = Chr(209)

Else

TrueChar$ = Chr(151)

End If

Case 2

FalseChar$ = "B"

If a Then

TrueChar$ = Chr(208)

Else

TrueChar$ = Chr(150)

End If

Case 3

FalseChar$ = "A"

If a Then

TrueChar$ = Chr(210)

Else

TrueChar$ = Chr(147)

End If

Case 4

FalseChar$ = "@"

If a Then

TrueChar$ = Chr(211)

Else

TrueChar$ = Chr(148)

End If

Case 5

FalseChar$ = ">"

If a Then

TrueChar$ = Chr(212)

Else

TrueChar$ = Chr(145)

End If

Case 6

FalseChar$ = "="

If a Then

TrueChar$ = Chr(213)

Else

TrueChar$ = Chr(146)

End If

Case Else

End Select

'Find and replace

WordBasic.EditFind Find:=FalseChar$, MatchCase:=1, PatternMatch:=0

While WordBasic.EditFindFound()

ThisChar = Asc(WordBasic.[Selection$]())

If ThisChar = 40 Then

WordBasic.WW6_EditClear

WordBasic.Insert TrueChar$

End If

WordBasic.EditFind

Wend

Next i

'MACRO ENDS HERE

'MACRO FOR WORD 6 and 95 STARTS HERE

EditFindClearFormatting

EditReplaceClearFormatting

StartOfDocument

'Check for platform

a = InStr(AppInfo$(1), "Macintosh")

For i = 1 To 6

'Set find and replace variables

Select Case i

Case 1

FalseChar$ = "C"

If a Then

TrueChar$ = Chr$(209)

Else

TrueChar$ = Chr$(151)

End If

Case 2

FalseChar$ = "B"

If a Then

TrueChar$ = Chr$(208)

Else

TrueChar$ = Chr$(150)

End If

Case 3

FalseChar$ = "A"

If a Then

TrueChar$ = Chr$(210)

Else

TrueChar$ = Chr$(147)

End If

Case 4

FalseChar$ = "@"

If a Then

TrueChar$ = Chr$(211)

Else

TrueChar$ = Chr$(148)

End If

Case 5

FalseChar$ = ">"

If a Then

TrueChar$ = Chr$(212)

Else

TrueChar$ = Chr$(145)

End If

Case 6

FalseChar$ = "="

If a Then

TrueChar$ = Chr$(213)

Else

TrueChar$ = Chr$(146)

End If

Case Else

End Select

'Find and replace

EditFind .Find = FalseChar$, .MatchCase = 1, .PatternMatch = 0

While EditFindFound()

ThisChar = Asc(Selection$())

If ThisChar = 40 Then

WW6_EditClear

Insert TrueChar$

End If

EditFind

Wend

Next i

'MACRO ENDS HERE

_________________________________________

READERS WRITE

Donna Payne wrote:

In response to readers write about Track Changes in Word 2002:

Although Microsoft has removed the option for how deleted text should appear in this version due to markup balloons, we have a free pdf file at the following location that explains how to get around this:

http://www.payneconsulting.com/public/tips/TipDetail.asp?nTipID=82.

Donna Payne

President

Payne Consulting Group, Inc.

www.payneconsulting.com

___________________

Johanna Murphy wrote:

In answer to Mary Eberle's comments regarding AutoCorrect in you previous newsletter, I would like to give you my comments on this subject. I also have been using AutoCorrect heavily in Word 97, and I copied my normal over. The problem I have is just the opposite. The formatted entries freeze up the program, but the unformatted all work. Especially the entries I have for inserting fields. For instance, I create a date by using the field Month Date and Year. I then copy it into the AutoCorrect box and tell it to be formatted, but it will turn it into unformatted or freeze up the program. I really hate that! Any suggestions would be appreciated.

While I've got your attention, I am also hoping you or your readers could help me with a problem in Word XP. I work for a law firm and when we had Word 97, I had created the firm's letterhead templates, pleading templates, etc. I inserted comments into the templates for the other users' convenience. When the templates were transferred to Word XP, the comments showed up as a thin vertical line on the screen, and the lines ALSO PRINTED! Every time I open a template it is set to "Final Markup." Since then, I have learned to use the Reviewing Toolbar to set the document to "Final Document." This procedure is very tiresome to always have to remember to switch to Final Document. Staff and attorneys call me all the time to ask why these vertical lines show up when they print something. I have deleted the comments out of the templates, but the lines still show up unexpectedly on the printed documents even though they don't show on the screen anymore. Is there help for this? Thanks.

Thanks to Donna for the additional information and to Johanna for her questions.

_________________________________________

RESOURCES

If you're having problems importing documents from other word processing programs into Microsoft Word, some of the document converters from Microsoft may help:

http://office.microsoft.com/downloads/default.aspx?Product=Word&Version=95|97|98|2000|2002&Type=Converter|Viewer

Before Word 2002, it was possible to set revision-tracking colors and formatting separately for inserted and deleted text. The procedure was simple:

1. Click Tools / Track Changes / Highlight Changes / Options.

2. Select "Mark" (bold, italic, underline, or double underline) for "Inserted text."

3. Select "Color" (various) for "Inserted text."

4. Select "Mark" (bold, italic, underline, or double underline) for "Deleted text."

5. Select "Color" (various) for "Deleted text."

6. Click the "OK" button.

In Word 2002, however, this feature works only for "Inserted Text." "Deleted text" automatically follows suit, and there seems to be no way to set the two independently. To make matters worse, Strikethrough is no longer among the listed marking options. How annoying! Fortunately, there's a hidden way to overcome these limitations. I've exploited it in the following macro, which you can easily modify to meet your own needs:

Sub SetTrackingFormat()
With Options
.InsertedTextMark = wdInsertedTextMarkUnderline
.InsertedTextColor = wdBlue
.DeletedTextMark = wdDeletedTextMarkStrikeThrough
.DeletedTextColor = wdRed
End With
End Sub

If you don't know how to use macros like that one, you can learn how here.

The macro is currently set to mark insertions as blue text with underline, and to mark deletions as red text with strikethrough. To change this, replace the "Underline" on the end of "wdInsertedTextMarkUnderline" or the "StrikeThrough" on the end of "wdDeletedTextMarkStrikeThrough" with any of the following:

Bold

ColorOnly

DoubleUnderline

Italic

None

StrikeThrough

Underline

Then replace "wdBlue" or "wdRed" with any of the following:

wdBlack

wdBlue

wdBrightGreen

wdByAuthor

wdDarkBlue

wdDarkRed

wdDarkYellow

wdGray25

wdGray50

wdGreen

wdNoHighlight

wdPink

wdRed

wdTeal

wdTurquoise

wdViolet

wdWhite

wdYellow

Then run the macro (Tools / Macro / Macros). Hah, hah! Once again Microsoft Word must bend to your will!

_________________________________________

READERS WRITE

Readers have sent so many great tips and comments that it's taking a while to go through them all. They'll be appearing in the newsletter over the next few weeks. Today's issue makes a good start, however. Many thanks to Bill Rubidge, Rohn Solecki, and Rebecca Evans for their terrific comments and tips.

Referring to the December 18, 2002, issue of Editorium Update, which featured styles and style lists from readers, Bill Rubidge (wbr@aya.yale.edu) wrote:

Eric Fletcher explains that he uses an "Editorial Note" style. We use something similar, but the style is called "Open Issue". (Actually, the name has a prefix, so that all the styles we use are sorted together in the list and distinguishable from styles that may come from other templates or users). The style highlights items with color, as Eric's does, but we do one thing more.

At the end of our documents, we insert a page break and then type a title "Open Issues". Below that, we generate a TOC based only the Open Issue style (not any headings--TOC field {TOC t "wbrOpenIssue,1"}). This gives us a complete list of these open issues for the entire document, to ensure that none are overlooked.

By the way, we also insert these Open Issue paragraphs (which are sometimes just queries) ABOVE the item in question, and the Open Issue style has the paragraph set to "keep with next". This helps make the page number refs in the Open Issue TOC more accurate.

If you really want to get complicated, on multi-file projects (we deal with about 40 files per book), it may be easier to just extract the open issues from the file and put them into another document. For now, I just do this using the open issue TOC at the end of each file, but have a macro that copies it (fields unlinked) to the clipboard and then opens up our Open Issue file (in Excel, for easier sorting). Based on posts in the Word PC listserve, I think involving Maggie Seneca, I think you could also harvest all the Open Issue items in the file and automatically write them to another file (rather than the manual paste we're using).

You might refer to the macro that Bryan and Pieter helped Eve Golden with, back in the Daily Word Tips list. I think the last posts about it were from November 20. That macro searches for text highlighted in a certain way, and copies all that text and appends it to a separate file.

_______________

Rohn Solecki wrote:

I also have a favorite style you might want to pass on. Although it may not be useful to the publishing industry, it is handy for internal documentation in companies that still use "green screen" computer terminals. Green screen terminals are the old style fixed pitch font, by default 24 line by 80 character displays (but optionally up to 27 lines by 132 characters).

Rather than doing a graphic screen capture I do a Edit / Select All, Edit / Copy to capture the text, paste to Word, then apply my "Screen Print" paragraph style to reasonably simulate the appearance of text on the computer terminal. This style has 3 main advantages over pasting a graphic screen capture:

* It uses orders of magnitude less space, which is important if you have lots of screens to capture.

* It is editable, so if something on screen changes you don't have redo the capture.

* Since it is editable, it is easy to apply character formatting like highlighter or font colors to highlight specific sections (without having to use a separate graphics program).

Details of Screen Print Paragraph Style:

* Paragraph Formatting - Flush Left, Keep with Next, Keep lines together, Border: box (single line), Shading: 5%, Indent: Hanging 0.25 Right 0", Widow and Orphan Control. Font Formatting - Courier, 10 pt, Condensed 0.5 pt.

Reasons for choices:

* The Box Border and 5% Shading simulate the look of the screen.

* Keep Lines together and Keep with next ensure that the whole screen capture stays on same page.

* Hanging indent is optional if a line wraps for some reason, for example, capturing from a 132-character display.

* Courier is fixed pitch so characters line up as they did on screen.

* 10 pt Condensed 0.5pt so that an 80-character line will fit on a page with reasonable margins (less than the default 1.5" both sides) without wrapping.

_______________

Rebecca Evans (evansreb@earthlink.net) wrote:

I have been designing and typesetting books for a living since 1976. Being able to use style tags in today's programs is certainly a blessing compared to keeping a spec sheet beside you so you can hand key specs as you re-type a book from a typemarked manuscript.

My comment on the style naming issue is that I have found I do not need list tags that add space after the list (NL End), just the tag to begin the list and for the interior paragraphs. All I need after lists, boxes, and the like, are two Body Text tags with added space above them, one with a paragraph indent and one without, because any paragraph style other than Body Text--heads, extracts, boxes, summaries, other lists--already includes space above.

Of course this assumes that spacing is consistent within a design so that you don't have +12' below a BL and +6' below an NL. And, I realize this may not be applicable to documents other than books. However, in my experience with textbooks, I have found those two extra Body Text styles to be all the "exit" styles I need.

On another note, I use two character style names because that lets me reduce the width of the style tag window (I use Ventura Publisher and keep the style list docked and open on screen), leaving more screen width to display page spreads. This is not an issue if you use a style drop down menu but I thought I'd throw in my two cents on that one too.

I responded, "Not being a Ventura user myself, I'd like to know why Ventura users want to tag Word files before bringing them into Ventura. Won't Ventura import RTF files? Any light you could shed on that subject for me?"

Rebecca replied:

Ventura does import RTF files--it will even File:Open RTF files and build copies of all the Styles as closely as possible to how they are in Word. Irrespective of that, you elucidated the reasons for using raw codes very well in your recent essay.

Most books are Styled erratically by the author and there is usually so much junk left in text files that it's easier to clean up the text if you can see the raw codes. Much of what I clean up is taken care of by EKTPlus but I still like to see exactly what I'm importing before I import it.

Also, an author's Styles, even if perfectly applied, never match the design of the typeset book. It is far easier for me to type codes than to drop down the Style list and click each one. Assign Styles to buttons takes a long time and would be almost as much work to use as dropping down the style list.

I use XyWrite for coding text files because I can drop in coding with short-cut keys, which are incredibly easy to assign in XyWrite: no menus, just select the text, press F2, press the key you want to use for that shortcut (any key), then press F3 to deselect the text. Then it's just ALT+"that key" to insert the text. You can keep reassigning new text to your shortcut keys as you work.

XyWrite also has macro-scripting capabilities that let me build S&R tables for almost anything. I keep the S&R table open in a separate window while I work so I can change/add entries in it as I go along.

Unfortunately, XyWrite is ASCII and everything else in the world (seemingly) is ANSI so I've recently been converting over to coding in Word. Assigning and using shortcut keys is more of a process in Word because alphanumeric keys are used for Word function shortcuts.

I should tell you that XyWrite is an older program used mostly by programming types now. XyWrite is DOS-based so I don't know if it will even run under Windows XP. It's an old friend for me but someone trying to learn it today probably wouldn't know what to do with the command line at the top of the screen (very useful if you know DOS commands) and would have to adjust to using function keys rather than the CTRL/ALT keys to execute commands.

There are folks out there who write scripts for converting Word coding to Ventura--Allan Shearer in Canada comes to mind--but your programs are so well executed and beautifully interfaced that it's worth paying for them even if the same functions are available free from other sources.

_________________________________________

RESOURCES

RMIT University has an excellent collection of links related to editing and publishing:

http://www.rmit.edu.au/links/publish.htm

Some weeks ago I suggested the need for a "wildcard dictionary" and asked readers to send in their contributions. You can read that article here:

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

I heard from Rosalie Wells, Hilary Powers, Eric Fletcher, Allene Goforth, Michael Coleman, and Steve Hudson, who sent some great wildcard strings and commentary on their use. Many thanks to them, and, if I missed anyone, many apologies.

You can learn more about finding and replacing with wildcards in these back issues of Editorium Update:

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

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

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

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

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

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

And now, the wildcard dictionary entries! (Before using any of these in the real world, be sure to try them on some test documents to make sure they will do what you need. You should do that with any wildcard string, of course.)

___________________________________

ROSALIE WELLS wrote:

I use this one all the time in my translations into Spanish to change the decimal separator "period" to a "comma" separator as required for many Spanish-speaking countries:

Find what: ([0-9]).([0-9])

Replace with: 1,2

___________________________________

HILARY POWERS wrote:

I tend to design strings from scratch when needed, but here are a couple that I use often enough to more or less remember them:

.([A-Z])|. 1

opens up initials on reference lists; requires fixing things like U.S. and N.Y. after

([0-9]). |^t1.^t

indents hand-typed list numbers

[!.]^013 - review one by one and add periods by hand where needed. There's a way of scanning for more end-sentence punctuation and doing the change automatically, but I'm usually too lazy to look it up and this is what I remember. A complete punctuation scan would be quite welcome. . . .

It'd be a good idea to emphasize that the Wildcard and Revision Tracking features do bad things to each other, at least in Word 97. Some simple replaces will work with tracking on, but it's hard to predict which ones are safe and which ones will scramble the new info. Before running any wildcard replace operation, it's best to save the file and then turn the tracking off. Run the replace, check to see if it worked, then TURN THE TRACKING BACK ON.

___________________________________

ERIC FLETCHER wrote:

I have my favourites in various Word files I seem to never get around to consolidating. But here are a few I found without having to look very hard:

DESCRIPTION: Finding a telephone number formatted as 123-4567.

FIND WHAT: ([0-9]{3})(-)([0-9]{4})

REPLACE WITH:

KEY WORDS: Telephone number

BEFORE:

AFTER:

COMMENTS: This is handy for doing a quick review of phone numbers. In Word 2002, you can choose to select all occurrences so you can see them easily in context.

DESCRIPTION: Changing telephone numbers formatted as (123) 456-7890 or (123)456-7890 to 123-456-7890.

FIND WHAT: ([(])([0-9]{3})([)])(*)([0-9]{3})(-)([0-9]{4})

REPLACE WITH: 2-567

KEY WORDS: Telephone number

BEFORE: Telephone numbers formatted as (123) 456-7890 or (123)456-7890.

AFTER: Telephone numbers formatted as 123-456-7890 or 123-456-7890.

COMMENTS: Note that the (*) looks after catching situations where there may or may not be a space after the area code portion.

DESCRIPTION: Find formatted text and change it to use HTML codes.

FIND WHAT: Font=Italic

REPLACE WITH: ^&

KEY WORDS: Italic, HTML, formatting

BEFORE: Change the italicized words to use HTML codes.

AFTER: Change the italicized words to use HTML codes.

COMMENTS: If you include Font=Not italic in the Replace with, the italics will be removed as well. Use variations of this for any formatting and other HTML codes.

DESCRIPTION: Find text coded with HTML and change it to Word formatting.

FIND WHAT: ()(*)()

REPLACE WITH: 2 Font=Italic

KEY WORDS: HTML, italic, formatting

BEFORE: Change the italicized words to regular Word formatting.

AFTER: Change the italicized words to regular Word formatting.

COMMENTS: Use variations of this for any formatting and other HTML codes.

___________________________________

ALLENE GOFORTH wrote:

Here are five of my wildcard routines. I use more than those, but some are specific to various publishers, and others are of the half-baked variety.

DESCRIPTION: In APA-style references lists, find volume numbers in roman and change them to italic. Retain the issue numbers in roman.

FIND WHAT: , [0-9]{1,}

REPLACE WITH: [nothing]; change font to italic

KEY WORDS: APA, references, volume numbers

BEFORE: Developmental Neurobiology, 13(2)

AFTER: Developmental Neurobiology, 13(2)

COMMENT: Find string includes a space between the first comma and the bracket.

DESCRIPTION: In APA-style references lists, find issue numbers in italics and change to roman.

FIND WHAT: ([0-9]@)

REPLACE WITH: [nothing]; change format to roman

KEY WORDS: APA, references, issue numbers

BEFORE: Developmental Neurobiology, 13(2)

AFTER: Developmental Neurobiology, 13(2)

DESCRIPTION: In APA-style references lists, find initials in names that need a space inserted after the period.

FIND WHAT: ([A-Z].[!A-Z])

REPLACE WITH: 1

KEYWORDS: APA, references, initials

BEFORE: Brown, A.C.

AFTER: Brown, A. C.

COMMENTS: A space is needed at the beginning of the Replace string.

DESCRIPTION: In APA-style references lists, find name strings containing "&" that need commas inserted before the "&."

FIND WHAT: ( [&])

REPLACE WITH: ,1

KEY WORDS: APA, references, &, comma

BEFORE: Smith, A. B. & Gordon, D. J.

AFTER: Smith, A. B., & Gordon, D. J.

COMMENTS: In the Find string, there is a space between the opening parenthesis and the bracket.

DESCRIPTION: Find and close up space between journal volume number and issue number in APA-style references lists.

FIND WHAT: (([0-9]@))

REPLACE WITH: 1

KEY WORDS: APA, references, space, volume, issue

BEFORE: 45 (3)

AFTER: 45(3)

COMMENTS: In the Find string there should be a space before the opening parenthesis. There should not be a space before the first character in the Replace string.

___________________________________

MICHAEL COLEMAN wrote:

Right now I'm working on an index. There's not a lot of work to be done, but it was exported from Quark to Word, so all the formatting was stripped. (If there's a way to avoid that, I'd love to learn about it.) So I set styles for the four levels. Simple enough. The only other trick is to get back all of the italics. There are a few titles that need to be italicized, and fortunately I know that they all have names with at least three words, so I searched for a string

[A-Z]([a-z]@) [A-Z]([a-z]@) [A-Z]

I didn't make any automatic changes because several titles fit the string but don't get italicized.

We used to have a lot of tables, figures, and exhibits in our books, but now they're all called figures. In the index, the appropriate first letter--t, f, or e--appeared in italics after the page number, such as 11-11e. (We use chapter-page pagination.) So I searched for

([0-9])[e,f,t]

I set the replace string to italic and replaced with

1f

Then I searched for ([0-9]) formatted as italic and changed it back to roman using 1.

Our old style was to use en dashes to show a range of pages, but that was hard to read because of the hyphens in the chapter-page pagination format. So we changed it to "to." I therefore searched for

^=([0-9])

And replaced it with

to 1

___________________________________

STEVE HUDSON wrote:

Remove Time stamping from most logs:

F: [[]*[]]

R: nothing

Kill excessive blank paras

F: ^p^p^p

R: ^p^p

Locate some passive voice instances

Find: be <*ed>

Convert a list of Firstname Lastname to Initial. Lastname

Find <(?)(*)> <(*)>

Replace 1. 3

Find manually formatted numbering (hand tweak)

F: [0-9]@.^t

R: Pass 1 List style, pass 2, nil.

Straight Quotes to Curly Quotes

To turn curlies to straight:

1. Turn off the Autocorrect

2. Go to your find and replace dialog and replace " with ".

Sharon Key wrote asking why, after selecting smart quotes, her find and replace of quotes with themselves didn't work to trigger the replacement from straight to curly. Yes, your FnR (find and replace) is NOT triggering the smart quote function. To do that it needs something before or after the quote to help the smart quote system dope it out. It's actually triggered by an "end of word" condition. So to replace straight quotes with curly quotes, use these FnR's with Wildcards enabled (select More and then look at options near the lower left)

Find: "(<*>)

Replace: "1

Find: ([! ])"

Replace: 1"

Both formulae use the () to force capture of that segment to be referred to in the replace section as 1 (or whatever left -> right position it holds if there are multiple bracketed entries).

The first finds quotes followed by a word ( a < is a start of a word, * is anything, a > is the end of a word), and replaces the quote with the word (now referred to as 1 from being bracketed) after it. You can't use that same trick for the second, as it selects the whole string of words afore it, and the smart quote feature is confused as the last typed character was in a range. So, we find any non blank character followed by a quote, and replace the single character and the quote. This will take care of most of your problems.

FnR CheatSheet

?= Any 1 character

*=Any string of characters

@ any number of repeats of the previous character

<=the beginning of a word

=the end of a word

{n}=n repeats of the previous char

{n,}=at least n repeats

{n-m}= between n and m repeats

[ ] marks a set of characters. A - used inside this means an ascending range between the two hyphenated characters. A !, only valid at the set's start, means 'any character except'.

() groups the expressions and indicates the order of evaluation. It is used with the n wildcard to rearrange expressions. The result of the 1st () pair is represented by 1, the next pair 2 and so on.

The easiest way is to use a special character as a literal, e.g. to find a bracket character, use ASCII code 40 instead. ASCII codes are specified in ANY sort of search with the caret ^.

= ^92

(=^40

)=^41

?=^63

{=^123

}=^125

[=^91

]=^93

@=^64

<=^60

=^62

*=^42

^=^94

To find some relevant information in Word's help file, Contents > Editing and Sorting text > Finding and Replacing Text. A few links later you can get some wildcard information.

10{1,3} finds "10", "100", and "1000".

[10]@ finds any binary number

<[a-zA-Z]{1,3}> finds words of three letters or less.

<[A-Z][a-z]@> finds any title-cased word.

<[0-9]@> finds any whole number, <[0-9]{1,3}> from 0-999

Find: <([0-9]@[/.-])([0-9]@[/.-])([0-9]@>)

Replace with: 2 1 3

Changes all numeric dates from DD/MM/YY(YY) to MM/DD/YY(YY) and back again.

_________________________________________

READERS WRITE

Readers have sent so many great tips and comments that it's taking a while to go through them all. They'll be appearing in the newsletter over the next few weeks. Thanks for your patience.

_________________________________________

RESOURCES

There's an excellent explanation of how to find and replace with wildcards at the Microsoft Word MVP site:

http://www.mvps.org/word/FAQs/General/UsingWildcards.htm

After publishing last week's article on creating a standard style list, I received such amazing feedback that I decided to dispense with a feature article this week and go straight to the Readers Write column. There's enough information here to keep you reading, thinking, and implementing for some time, and I owe my thanks in particular to Eric Fletcher, LeAnne Baird (with comments from Roger Shuttleworth), and Wordmeister Steve Hudson. Enjoy!

ADDITIONAL STYLES FOR A STANDARD LIST

Eric Fletcher (chesley@attcanada.ca) wrote:

Wow, your style list would be a great reference for parts of books, let alone for managing the format!

I have a couple that we use that you might also consider.

Photo box

Used to identify an image by its file name or reference number. I usually have this set up in red text with a red box around it because if you zoom out (Ctrl-Scrollwheel), they are very visible even when the rest of the copy turns to black lines. When we are trying to "populate" a book with images, it can be a handy way to see if there are any gaping holes. If we are doing the layout with the images in Word, this is handy because I can put in the file name, then convert it to the includepicture field after we've dealt with the text of the file. If we are providing the images, we can provide information that helps in the layout (file name on CD, pixel dimensions & colour depth; identity and format of original art...)

Editorial note

Used for a note to the editor (or reviewer) about something we came across during the layout or editing. We have it set the copy in a light green filled box in Arial Narrow type so it is very visible on screen and quite visible if printed. It is also easy to spot in a very reduced view (as above) but I also have an associated button that finds the next "Editorial note" style to be able to quickly review them. The editorial note has been much more useful to us than Word's comments or review functions as many of our documents get sent out as paper copies. As well, many are being reviewed by people whose first language is not English (or French) so we often find ourselves having to be "diplomatic" in querying the intended meaning. (Some of the content is very technical so we cannot presume to be subject matter experts even if we see something that is clearly not correct--I'm sure you've had this experience now and then . . . ) This style enables us to copy a sentence and rework it as a "suggestion." If they agree, they don't have to write it themselves--and we don't have to try to decipher their writing!

MANAGING STYLES WITH WORD 2002'S "STYLES AND FORMATTING" TASK PANE

Eric also wrote:

I discovered a feature of Word 2002 that I'd hitherto overlooked--and it was so useful I thought I should share it with you.

With Word's task pane set to "Styles and formatting" and the bottom pull-down set to "Formatting in use", you are presented with what at first appears to be an often long and useless list of all of the variations of different formatting within the document. But when you select one of the items in this list (labelled "Pick formatting to apply"), instead of clicking on the format summary to apply it, right-click it and examine the pull-down menu that appears. From it, you can choose Modify and some other options, but the top line both shows how many instances of the selected format occur in the document AND gives you the opportunity to select all of them at once. Once selected of course, you can apply a style or do some other action on the whole set.

As an example, when I noticed that the panel listed both "Heading 3" and "Heading 3 + underline", choosing to select all 11 instances of the latter let me change all eleven of the instances of underlining contained within the Heading 3 style to no underline and italic instead--in one single action.

Of course, I could have done the same thing with find and replace but this is much faster and lets me see formatting issues that I might otherwise have overlooked. For example, I frequently end up selectively tweaking character spacing (condensing the font) or slightly reducing inter-paragraph spacing in several places throughout a document to manually adjust to fit text for a final print layout. Getting rid of such things for subsequent use of the content is complicated because they are not evident. This task pane feature makes it simple: all of the variations are listed and I can do all of it from the panel without potentially losing other formatting I do want to retain. (As would be the case with superscripts and the like if they were within a selection and I just used Ctrl-Space to reset the font for example.) My panel showed all such variations as "Condensed by 0.1 pt" as well as "Condensed by 0.25 pt" and "Block indent + Before: 5 pt" so it was easy to reset them to the normal conditions. As you do so, the list gets shorter until (ideally) you are left with only the standard style list with allowable variants like italics within them.

In addition to Formatting in use, the other options at the bottom of the task pane in this view let you see Available styles (just the styles), Available formatting (the styles plus variants), All styles (your own plus default ones), and Custom (lets you select what to display). All-in-all, a very powerful tool for anyone who is serious about managing style usage in a Word document.

PARAGRAPH NAMING SCHEMES

LeAnne Baird wrote:

The paragraph naming scheme below is a pain to implement because legacy documents may need to have their styles replaced, but we bit the bullet and did it in one team I was on just because it is SUCH an elegant solution--so elegant that I've used it at every new company since we did the first one, and so have many of the other team members in *their* subsequent assignments.

🙂 Note: I've never used a complete template that didn't have more than 100 and less than 120 styles. Seems always to come out about the same regardless of the subject matter or document type!

1. Rename each paragraph (and character) style with a two-letter prefix followed by a space. Begin master and reference page styles with z or x +[letter or number] to send them to the bottom of the list.

2. Tag paragraphs from the keyboard by pressing F9, entering the prefix, and pressing Enter (or you may need to press one or two down arrows, see below). The desired style is applied.

This strategy makes the shortcuts easy to memorize through frequent use because we try hard to be logical, with the exception of "aa body," so named because it can always float to the top of the list. If you're forced to scroll for something, at least you can get close with F9+one key.

aa body

b1 bullet 1st level

b2 bullet 2nd level

bp bullet para

bp bullet para 2 (F9+bp+Down Arrow)

h1 heading 1

h2 heading 2

tb table body

th table heading

t1 table bullet 1

tp table bullet 1 para

s1 step 1

s2 subsequent steps

zc Chapter name

zn Chapter number

I am about finished with a MS Word template with customized style and table-insert toolbars so that our non-writer internal customers can easily use the same styles to produce consistently styled documents. These documents then (ZIP!) import right into Frame and lay themselves out with only minor nudges for print and PDF, and (ZIP!) right out through WWP to reformat as online Help systems.

By the way, for organizations looking toward the XML future, these are the considerations in style naming according to the quick-and-dirty search I did. Some of the major databases (SQL, Oracle, Sybase) do not support underscores in XML tag names, and for SQL processing XML tag names must start with two alpha characters. Of course, use no special characters, and this includes hyphens. Mixed case would seem to be OK, but the suggestion is that all the style names be mixed case if some are. (I can't imagine why this would make a difference, but who knows what lurks inside those db engines.) Also, in the XML naming specs, titles should not be longer than 30 characters for Sybase and Oracle, 18 for Informix.

In corresponding with LeAnne about this, Roger Shuttleworth noted:

Some folks suggest that you should keep paragraph (and character) format names to one word. One reason for this is that XML tags cannot contain spaces, and you may want to (ZIP!) them across to XML in some way in the future, perhaps as attributes. So I use an underscore rather than a space, and run the words together, such as RI_ReferenceInfo.

STANDARD STYLE LISTS FOR PUBLICATION TYPES

Steve Hudson was good enough to share his standard style lists for a variety of publication types, including the formatting for the styles!

PUBLISH TYPE: DRAFT

Body Text: Generic + Font: Arial, Hyphenate, Outline numbered, Tabs: 0 cm

Body Text C: Generic + Font: Arial, Centered, Hyphenate

Body Text R: Generic + Font: Arial, Flush Right, Hyphenate

Code: Default Paragraph Font + Font: Courier New, 10 pt, Underline color: Auto, No Proofing, Raised 1 pt, Font color: Auto, English (Australia), No effect, Pattern: Clear

Copyright: Generic + Font: Arial, 7 pt, Space before 0 pt after 0 pt, Hyphenate

Default Paragraph Font: The font of the underlying paragraph style + English (Australia)

Emphasis: Default Paragraph Font + Font: Bold, Not Italic, Underline color: Auto, Font color: Auto, No effect, Pattern: Clear

FollowedHyperlink: Default Paragraph Font + Font: Not Italic, Underline, Underline color: Auto, No Proofing, Font color: Gray-50%, No effect, Pattern: Clear

Footer: Header +

Generic: Font: Times New Roman, 10 pt, English (Australia), Kern at 10 pt, Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Don't hyphenate

Glossary: Default Paragraph Font + Underline color: Auto, Font color: Auto, No effect, Pattern: Clear

Header: Generic + Font: Arial, Tabs: 7.3 cm centered, 14.64 cm right flush

Heading 1: Heading 4 + Font: 26 pt, Indent: Hanging 0.74 cm, Space before 18 pt after 21 pt, Level 1, Outline numbered, Tabs: 0.74 cm

Heading 1 No TOC: Generic + Font: Verdana, 26 pt, Bold, Space before 18 pt after 21 pt, Keep with next, Not Keep lines together

Heading 2: Heading 4 + Font: 22 pt, Indent: Hanging 0.74 cm, Space before 18 pt after 15 pt, Level 2, Outline numbered, Tabs: 0.74 cm

Heading 2 No TOC: Generic + Font: Verdana, 22 pt, Bold, Space before 18 pt after 15 pt, Keep with next, Not Keep lines together

Heading 3: Heading 4 + Font: 16 pt, Indent: Hanging 0.74 cm, Space before 18 pt after 15 pt, Level 3, Outline numbered, Tabs: 0.74 cm

Heading 4: Generic + Font: Verdana, 12 pt, Bold, Space before 6 pt after 6 pt, Keep with next, Not Keep lines together, Level 4

Heading 5: Heading 4 + Space before 3 pt, Level 5

Heading 6: Heading 4 + Space before 3 pt, Level 6

Heading 7: Heading 4 + Space before 3 pt, Level 7

Heading 8: Heading 4 + Space before 3 pt, Level 8

Heading 9: Heading 4 + Space before 3 pt, Level 9

Heading-table-centred: Heading-table-left + Centered

Heading-table-left: Generic + Font: Arial Narrow, 13 pt, Bold, Hyphenate

Heading-table-right: Heading-table-left + Flush Right

Hyperlink: Default Paragraph Font + Font: Not Italic, Underline, Underline color: Auto, No Proofing, Font color: Blue, No effect, Pattern: Clear

Index 1: Generic + Font: Arial, Hyphenate

Index 2: Generic + Font: Arial, Indent: Left 0.74 cm First 0.74 cm, Hyphenate

Index 3: Generic + Font: Arial, Indent: Left 1.48 cm First 1.48 cm, Hyphenate

Input: Default Paragraph Font + Font: Tahoma, 9 pt, Bold, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

KeyPress: Default Paragraph Font + Font: Tahoma, 9 pt, Bold, Underline color: Auto, Not Small caps, All caps, No Proofing, Font color: Auto, No effect, Pattern: Clear

List Bullet: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

List Number: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

List Number Outline: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

Microline: Normal + Font: 1 pt, Font color: White

Normal: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Flush left, Line spacing single, Widow/orphan control, Keep lines together, Suppress line numbers

Output: Default Paragraph Font + Font: Verdana, 9 pt, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

Page Number: Default Paragraph Font + Font: Arial, Bold, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

Subtitle: Title + Font: 18 pt, Space before 12 pt, Keep lines together

Terminal Screen: Generic + Font: Courier, 8 pt, No Proofing, Indent: Left 0.55 cm Right 0.55 cm, Space before 1 pt after 0 pt, Border: Top(Single solid line, Auto, 1 pt Line width), Bottom(Single solid line, Auto, 1 pt Line width), Left(Single solid line, Auto, 1 ...

TextBox: Generic + Font: Arial Narrow, Bold, Space before 0 pt after 0 pt, Hyphenate

TextBox C: TextBox + Centered

TextBox R: TextBox + Flush Right

Title: Generic + Font: Tahoma, 36 pt, Bold, Centered, Space before 72 pt after 12 pt, Not Keep lines together

TOC 1: Generic + Font: Verdana, 12 pt, Bold, No Proofing, Space before 18 pt, Keep with next, Not Keep lines together, Tabs: 0 cm, 14.64 cm right flush ...

TOC 2: TOC 1 + Font: Not Bold, Space before 3 pt after 0 pt, Keep lines together

TOC 3: TOC 2 + Font: 10 pt, Indent: Left 0.74 cm

TOC 4: TOC 3 + Indent: Left 1.48 cm, Space after 3 pt

TOC 5: TOC 2 + Font: 10 pt, Space after 3 pt

TOC 6: TOC 5 +

TOC 7: TOC 5 +

TOC 8: TOC 5 +

Version: Subtitle + Font: 14 pt, Not Bold, Space before 6 pt after 3 pt

PUBLISH TYPE: HELP

Body Text: Generic + Font: Arial, 12 pt, Hyphenate, Outline numbered, Tabs: 0 cm

Body Text C: Generic + Font: Arial, 12 pt, Centered, Hyphenate

Body Text R: Generic + Font: Arial, 12 pt, Flush Right, Hyphenate

Code: Default Paragraph Font + Font: Courier New, 12 pt, Underline color: Auto, No Proofing, Raised 1 pt, Font color: Auto, No effect, Pattern: Clear

Copyright: Generic + Font: Arial, 7 pt, Space before 0 pt after 0 pt, Hyphenate

Default Paragraph Font: The font of the underlying paragraph style + English (Australia)

Emphasis: Default Paragraph Font + Font: Bold, Not Italic, Underline color: Auto, Font color: Auto, No effect, Pattern: Clear

FollowedHyperlink: Default Paragraph Font + Font: Not Italic, Underline, Underline color: Auto, No Proofing, Font color: Gray-50%, No effect, Pattern: Clear

Footer: Header +

Generic: Font: Times New Roman, 10 pt, English (Australia), Kern at 10 pt, Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Suppress line numbers, Don't hyphenate

Glossary: Default Paragraph Font + Underline color: Auto, Font color: Auto, No effect, Pattern: Clear

Header: Generic + Font: Arial, Tabs: 7.3 cm centered, 14.64 cm right flush

Heading 1: Heading 4 + Font: 28 pt, Space before 18 pt after 21 pt, Level 1

Heading 1 No TOC: Generic + Font: Verdana, 28 pt, Bold, Space before 18 pt after 21 pt, Keep with next, Keep lines together

Heading 2: Heading 4 + Font: 24 pt, Space before 18 pt after 15 pt, Level 2

Heading 2 No TOC: Generic + Font: Verdana, 24 pt, Bold, Space before 18 pt after 15 pt, Keep with next, Keep lines together

Heading 3: Heading 4 + Font: 18 pt, Space before 18 pt after 15 pt, Level 3

Heading 4: Generic + Font: Verdana, 14 pt, Bold, Space before 6 pt after 6 pt, Keep with next, Keep lines together, Level 4

Heading 5: Heading 4 + Space before 3 pt, Level 5

Heading 6: Heading 4 + Space before 3 pt, Level 6

Heading 7: Heading 4 + Space before 3 pt, Level 7

Heading 8: Heading 4 + Space before 3 pt, Level 8

Heading 9: Heading 4 + Space before 3 pt, Level 9

Heading-table-centred: Heading-table-left + Centered

Heading-table-left: Generic + Font: Arial Narrow, 13 pt, Bold, Keep lines together, Hyphenate

Heading-table-right: Heading-table-left + Flush Right

Hyperlink: Default Paragraph Font + Font: Not Italic, Underline, Underline color: Auto, No Proofing, Font color: Blue, No effect, Pattern: Clear

Index 1: Generic + Font: Arial, 12 pt, Hyphenate

Index 2: Generic + Font: Arial, 12 pt, Indent: Left 0.74 cm First 0.74 cm, Hyphenate

Index 3: Generic + Font: Arial, 12 pt, Indent: Left 1.48 cm First 1.48 cm, Hyphenate

Input: Default Paragraph Font + Font: Tahoma, 11 pt, Bold, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

KeyPress: Default Paragraph Font + Font: Tahoma, 11 pt, Bold, Underline color: Auto, Not Small caps, All caps, No Proofing, Font color: Auto, No effect, Pattern: Clear

List Bullet: Font: Arial, 12 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

List Number: Font: Arial, 12 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

List Number Outline: Font: Arial, 12 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

Microline: Normal + Font: 1 pt, Font color: White

Normal: Font: Arial, 12 pt, English (Australia), Kern at 10 pt, Flush left, Line spacing single, Widow/orphan control, Suppress line numbers

Output: Default Paragraph Font + Font: Verdana, 11 pt, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

Page Number: Default Paragraph Font + Font: Arial, Bold, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

Subtitle: Title + Font: 18 pt, Space before 12 pt

Terminal Screen: Generic + Font: Courier, 8 pt, No Proofing, Indent: Left 0.55 cm Right 0.55 cm, Space before 1 pt after 0 pt, Border: Top(Single solid line, Auto, 1 pt Line width), Bottom(Single solid line, Auto, 1 pt Line width), Left(Single solid line, Auto, 1 ...

TextBox: Generic + Font: Arial Narrow, Bold, Space before 0 pt after 0 pt, Hyphenate

TextBox C: TextBox + Centered

TextBox R: TextBox + Flush Right

Title: Generic + Font: Tahoma, 36 pt, Bold, Centered, Space before 72 pt after 12 pt

TOC 1: Generic + Font: Verdana, 12 pt, Bold, No Proofing, Space before 18 pt, Keep with next, Tabs: 0 cm, 14.64 cm right flush ...

TOC 2: TOC 1 + Font: 10 pt, Not Bold, Proof Text, Space before 3 pt after 0 pt, Not Keep with next, Tabs:Not at 0 cm, 14.64 cm

TOC 3: TOC 2 + Indent: Left 0.74 cm

TOC 4: TOC 3 + Indent: Left 1.48 cm, Space after 3 pt

TOC 5: TOC 2 + Space after 3 pt

TOC 6: TOC 5 +

TOC 7: TOC 5 +

TOC 8: TOC 5 +

Version: Subtitle + Font: 14 pt, Not Bold, Space before 6 pt after 3 pt

PUBLISH TYPE: PRODUCT

Body Text: Generic + Font: Arial, Hyphenate, Outline numbered, Tabs: 0 cm

Body Text C: Generic + Font: Arial, Centered, Hyphenate

Body Text R: Generic + Font: Arial, Flush Right, Hyphenate

Code: Default Paragraph Font + Font: Courier New, 10 pt, Underline color: Auto, No Proofing, Raised 1 pt, Font color: Auto, No effect, Pattern: Clear

Copyright: Generic + Font: Arial, 7 pt, Space before 0 pt after 0 pt, Hyphenate

Default Paragraph Font: The font of the underlying paragraph style + English (Australia)

Emphasis: Default Paragraph Font + Font: Bold, Not Italic, Underline color: Auto, Font color: Auto, No effect, Pattern: Clear

FollowedHyperlink: Default Paragraph Font + Font: Not Italic, Underline, Underline color: Auto, No Proofing, Font color: Gray-50%, No effect, Pattern: Clear

Footer: Header +

Generic: Font: Times New Roman, 10 pt, English (Australia), Kern at 10 pt, Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Don't hyphenate

Glossary: Default Paragraph Font + Underline color: Auto, Font color: Auto, No effect, Pattern: Clear

Header: Generic + Font: Arial, Tabs: 7.3 cm centered, 14.64 cm right flush

Heading 1: Heading 4 + Font: 26 pt, Space before 18 pt after 21 pt, Level 1, Numbered, Tabs: 0 cm

Heading 1 No TOC: Generic + Font: Verdana, 26 pt, Bold, Space before 18 pt after 21 pt, Keep with next, Not Keep lines together

Heading 2: Heading 4 + Font: 22 pt, Space before 18 pt after 15 pt, Level 2

Heading 2 No TOC: Generic + Font: Verdana, 22 pt, Bold, Space before 18 pt after 15 pt, Keep with next, Not Keep lines together

Heading 3: Heading 4 + Font: 16 pt, Space before 18 pt after 15 pt, Level 3

Heading 4: Generic + Font: Verdana, 12 pt, Bold, Space before 6 pt after 6 pt, Keep with next, Not Keep lines together, Level 4

Heading 5: Heading 4 + Space before 3 pt, Level 5

Heading 6: Heading 4 + Space before 3 pt, Level 6

Heading 7: Heading 4 + Space before 3 pt, Level 7

Heading 8: Heading 4 + Space before 3 pt, Level 8

Heading 9: Heading 4 + Space before 3 pt, Level 9

Heading-table-centred: Heading-table-left + Centered

Heading-table-left: Generic + Font: Arial Narrow, 13 pt, Bold, Hyphenate

Heading-table-right: Heading-table-left + Flush Right

Hyperlink: Default Paragraph Font + Font: Not Italic, Underline, Underline color: Auto, No Proofing, Font color: Blue, No effect, Pattern: Clear

Index 1: Generic + Font: Arial, Hyphenate

Index 2: Generic + Font: Arial, Indent: Left 0.74 cm First 0.74 cm, Hyphenate

Index 3: Generic + Font: Arial, Indent: Left 1.48 cm First 1.48 cm, Hyphenate

Input: Default Paragraph Font + Font: Tahoma, 9 pt, Bold, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

KeyPress: Default Paragraph Font + Font: Tahoma, 9 pt, Bold, Underline color: Auto, Not Small caps, All caps, No Proofing, Font color: Auto, No effect, Pattern: Clear

List Bullet: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

List Number: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

List Number Outline: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

Microline: Normal + Font: 1 pt, Font color: White

Normal: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Flush left, Line spacing single, Widow/orphan control, Keep lines together, Suppress line numbers

Output: Default Paragraph Font + Font: Verdana, 9 pt, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

Page Number: Default Paragraph Font + Font: Arial, Bold, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

Subtitle: Title + Font: 18 pt, Space before 12 pt, Keep lines together

Terminal Screen: Generic + Font: Courier, 8 pt, No Proofing, Indent: Left 0.55 cm Right 0.55 cm, Space before 1 pt after 0 pt, Border: Top(Single solid line, Auto, 1 pt Line width), Bottom(Single solid line, Auto, 1 pt Line width), Left(Single solid line, Auto, 1 ...

TextBox: Generic + Font: Arial Narrow, Bold, Space before 0 pt after 0 pt, Hyphenate

TextBox C: TextBox + Centered

TextBox R: TextBox + Flush Right

Title: Generic + Font: Tahoma, 36 pt, Bold, Centered, Space before 72 pt after 12 pt, Not Keep lines together

TOC 1: Generic + Font: Verdana, 12 pt, Bold, No Proofing, Space before 18 pt, Keep with next, Not Keep lines together, Tabs: 0 cm, 14.64 cm right flush ...

TOC 2: TOC 1 + Font: 10 pt, Not Bold, Proof Text, Space before 3 pt after 0 pt, Not Keep with next, Keep lines together, Tabs:Not at 0 cm, 14.64 cm

TOC 3: TOC 2 + Indent: Left 0.74 cm

TOC 4: TOC 3 + Indent: Left 1.48 cm, Space after 3 pt

TOC 5: TOC 2 + Space after 3 pt

TOC 6: TOC 5 +

TOC 7: TOC 5 +

TOC 8: TOC 5 +

Version: Subtitle + Font: 14 pt, Not Bold, Space before 6 pt after 3 pt

PUBLISH TYPE: README

Body Text: Generic + Font: Arial, Hyphenate, Outline numbered, Tabs: 0 cm

Body Text C: Generic + Font: Arial, Centered, Hyphenate

Body Text R: Generic + Font: Arial, Flush Right, Hyphenate

Code: Default Paragraph Font + Font: Courier New, 10 pt, Underline color: Auto, No Proofing, Raised 1 pt, Font color: Auto, No effect, Pattern: Clear

Copyright: Generic + Font: Arial, 7 pt, Centered, Space before 0 pt after 0 pt, Hyphenate

Default Paragraph Font: The font of the underlying paragraph style + English (Australia)

Emphasis: Default Paragraph Font + Font: Bold, Not Italic, Underline color: Auto, Font color: Auto, No effect, Pattern: Clear

FollowedHyperlink: Default Paragraph Font + Font: Not Italic, Underline, Underline color: Auto, No Proofing, Font color: Gray-50%, No effect, Pattern: Clear

Footer: Header +

Generic: Font: Times New Roman, 10 pt, English (Australia), Kern at 10 pt, Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Don't hyphenate

Glossary: Default Paragraph Font + Underline color: Auto, Font color: Auto, No effect, Pattern: Clear

Header: Generic + Font: Arial, Tabs: 7.3 cm centered, 14.64 cm right flush

Heading 1: Heading 4 + Font: 15 pt, Space before 18 pt after 9 pt, Level 1, Numbered, Tabs: 0 cm

Heading 1 No TOC: Generic + Font: Verdana, 15 pt, Bold, Space before 18 pt after 9 pt, Keep with next, Not Keep lines together

Heading 2: Heading 4 + Font: 12 pt, Space before 18 pt, Level 2

Heading 2 No TOC: Generic + Font: Verdana, 12 pt, Bold, Space before 18 pt, Keep with next, Not Keep lines together

Heading 3: Heading 4 + Space before 18 pt, Level 3

Heading 4: Generic + Font: Verdana, Bold, Space before 6 pt, Keep with next, Not Keep lines together, Level 4

Heading 5: Heading 4 + Space before 3 pt after 6 pt, Level 5

Heading 6: Heading 4 + Space before 3 pt after 6 pt, Level 6

Heading 7: Heading 4 + Space before 3 pt after 6 pt, Level 7

Heading 8: Heading 4 + Space before 3 pt after 6 pt, Level 8

Heading 9: Heading 4 + Space before 3 pt after 6 pt, Level 9

Heading-table-centred: Heading-table-left + Centered

Heading-table-left: Generic + Font: Arial Narrow, 13 pt, Bold, Hyphenate

Heading-table-right: Heading-table-left + Flush Right

Hyperlink: Default Paragraph Font + Font: Not Italic, Underline, Underline color: Auto, No Proofing, Font color: Blue, No effect, Pattern: Clear

Index 1: Generic + Font: Arial, Hyphenate

Index 2: Generic + Font: Arial, Indent: Left 0.74 cm First 0.74 cm, Hyphenate

Index 3: Generic + Font: Arial, Indent: Left 1.48 cm First 1.48 cm, Hyphenate

Input: Default Paragraph Font + Font: Tahoma, 9 pt, Bold, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

KeyPress: Default Paragraph Font + Font: Tahoma, 9 pt, Bold, Underline color: Auto, Not Small caps, All caps, No Proofing, Font color: Auto, No effect, Pattern: Clear

List Bullet: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

List Number: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

List Number Outline: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Indent: Hanging 0.74 cm Flush left, Line spacing single, Space before 3 pt after 3 pt, Widow/orphan control, Keep lines together, Suppress line numbers, Outline numbered, Tabs: 0.74 cm

Microline: Normal + Font: 1 pt, Font color: White

Normal: Font: Arial, 10 pt, English (Australia), Kern at 10 pt, Flush left, Line spacing single, Widow/orphan control, Keep lines together, Suppress line numbers

Output: Default Paragraph Font + Font: Verdana, 9 pt, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

Page Number: Default Paragraph Font + Font: Arial, Bold, Underline color: Auto, No Proofing, Font color: Auto, No effect, Pattern: Clear

Subtitle: Title + Keep lines together

Terminal Screen: Generic + Font: Courier, 8 pt, No Proofing, Indent: Left 0.55 cm Right 0.55 cm, Space before 1 pt after 0 pt, Border: Top(Single solid line, Auto, 1 pt Line width), Bottom(Single solid line, Auto, 1 pt Line width), Left(Single solid line, Auto, 1 ...

TextBox: Generic + Font: Arial Narrow, Bold, Space before 0 pt after 0 pt, Hyphenate

TextBox C: TextBox + Centered

TextBox R: TextBox + Flush Right

Title: Generic + Font: Tahoma, 15 pt, Bold, Centered, Space before 0 pt after 0 pt, Not Keep lines together

TOC 1: Generic + Font: Verdana, 12 pt, Bold, No Proofing, Keep with next, Not Keep lines together, Tabs: 0 cm, 14.64 cm right flush ...

TOC 2: TOC 1 + Font: 10 pt, Not Bold, Proof Text, Indent: Left 0.74 cm, Space before 0 pt after 0 pt, Not Keep with next, Keep lines together, Tabs:Not at 0 cm, 14.64 cm

TOC 3: TOC 2 + Indent: Left 1.48 cm

TOC 4: TOC 3 + Space before 3 pt after 3 pt

TOC 5: TOC 2 + Indent: Left 0 cm, Space before 3 pt after 3 pt

TOC 6: TOC 5 +

TOC 7: TOC 5 +

TOC 8: TOC 5 +

Version: Subtitle + Font: 10 pt, Not Bold, Space after 3 pt

Again, thanks to one and all for the terrific tips and information.

Last week's newsletter explained the importance of using styles consistently in Microsoft Word, with a promise that this week I'd share my standard style list. As you look at the list, keep in mind that it was developed for styling books. If you work mostly on journals or magazines, your list will probably look quite different. I'm sharing my list primarily to give you an idea of what a fairly complete standardized list might look like. If you can use it or adapt it for what you do, great.

You'll notice that my style names are long. I've made them that way because I don't like trying to decipher names like HD1NI and BQ2. In some situations, however, that kind of brevity might be important, so do whatever works best for you. Sometimes, I've modified the names of built-in Word styles by adding a comma and then some descriptive text.

I've also modified the drop-down style list on Word's Formatting toolbar so it's nice and wide to accommodate those long style names. You can learn how to do that here:

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

I keep my styles in a template that I attach to any document I need to edit, and I've formatted the styles so they're easy on my middle-aged eyes. You can learn more about that here:

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

I'm also fond of using color in heading styles so I know at a glance whether I'm dealing with a first-, second-, or third-level subhead. You can learn more about that here:

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

As you review the list, you might wonder why I have so many variations of styles for block quotations, poetry, and a few other items. These are necessary for decent typography, as explained here:

http://www.editorium.com/editkit/TH_49.htm

The style named Normal,Text 1 is the basic body text for any book. It's named Normal,Text 1 rather than Normal for ease in importing documents into QuarkXPress, which uses a style named Normal that isn't always compatible with Word's Normal style. Many editors prefer to use a style named something like "Body Text" for the same reason.

Some of the styles end in "NI," which stands for "no indent." I use these to mark text that should have no paragraph indent. For example, Block Quote Start NI marks the first paragraph of a block quotation that begins somewhere in the middle of the paragraph being quoted. Normal Text 1 NI is used after a block quotation to mark text that does not begin a new paragraph but continues the thought of the text before the block quotation. Using these styles is the equivalent of writing "No paragraph" or "No indent" on a paper manuscript.

The name of each style is followed by a description of its function. The styles marked with an asterisk are the ones I use most often. If you'd like to see an actual Word template that includes such styles, you'll find one (named Typespec.dot) included with our Editor's ToolKit Plus program, which you can download here:

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

Feel free to use the template and modify it to suit your needs.

And now, here's the list:

Bib Subhead

Subheading separating different kinds of bibliographic entries. For example, a bibliography might include different entries under the subheadings of "Books," "Periodicals," and "Archival Materials."

Bib Text

The text of a bibliographic entry, such as "Pyle, Howard. *Salt and Pepper.* Harper and Brothers, New York, 1885."

*Block

A block quotation of one paragraph (indented).

*Block NI

A block quotation of one paragraph (not indented).

Block Heading

A heading at the beginning of a block quotation.

Block Subhead

A subheading between paragraphs of a block quotation.

*Block First

First paragraph of a block quotation (indented).

*Block First NI

First paragraph of a block quotation (not indented).

*Block Middle

Middle paragraph of a block quotation. The quotation may include more than one of these.

*Block Last

Last paragraph of a block quotation.

Block Source

Citation following a block quotation (usually someone's name).

Block Poem

A single line of poetry inside a block quotation.

Block Poem Heading

Heading before a poem inside a block quotation (usually the poem's title).

Block Poem Subhead

Subheading between stanzas of a poem inside a block quotation.

Block Poem First

First line of a poem inside a block quotation (possibly indented).

Block Poem First NI

First line of a poem inside a block quotation (possibly not indented).

Block Poem Start

Starting line of any poetry stanza but the first inside a block quotation (possibly indented).

Block Poem Start NI

Starting line of any poetry stanza but the first inside a block quotation (possibly not indented).

Block Poem Middle

Middle line of any poetry stanza inside a block quotation (possibly indented). The stanza may include more than one of these.

Block Poem Middle NI

Middle line of any poetry stanza inside a block quotation (possibly not indented). The stanza may include more than one of these.

Block Poem End

Ending line of any poetry stanza but the last inside a block quotation (possibly indented).

Block Poem End NI

Ending line of any poetry stanza but the last inside a block quotation (possibly not indented).

Block Poem Last

Last line of a poem inside a block quotation (possibly indented).

Block Poem Last NI

Last line of a poem inside a block quotation (possibly not indented).

Block Poem Source

Citation following a poem inside a block quotation (usually someone's name).

*Book Byline 1

A book's author. Used on the book's title page.

*Book Byline 2

A book's second author. Used on the book's title page.

Book Byline3

A book's third author. Used on the book's title page.

Book Byline4

A book's fourth author. Used on the book's title page.

*Book Publisher

A book's publisher (such as Random House or HarperCollins). Used on the book's title page.

Book Puff

A testimonial for the book. Used on the half-title page or jacket.

Book Puff Source

The name of a person giving the testimonial. Used under a book puff.

Book Puff Source Affiliation

The position or affiliation of a person giving the testimonial. Used under a book puff source.

*Book Series

The title of a series to which a book belongs, such as *The Lord of the Rings* (by J.R.R. Tolkien).

*Book Subtitle

A book's subtitle, such as *There and Back Again* (whose title is *The Hobbit*). Used on the book's title page.

Book Subsubtitle

A book's subsubtitle (yes, these do show up from time to time). Used on the book's title page.

Book Teaser

A line of marketing or explanatory copy. Used on the book's title page.

*Book Title

A book's title, such as *Fellowship of the Ring* (by J.R.R. Tolkien). Used on the book's title page.

*Caption

The caption under a photograph or other graphic.

*Chapter Number

The number of a chapter. See "Heading 1,Chapter Title."

Chapter Quote

A quotation at the beginning of a chapter.

Chapter Quote Source

A citation for a chapter quote. This is usually someone's name.

Chapter Subtitle

A subtitle after a chapter title (Heading 2,Chapter Title).

Chapter Subsubtitle

A subtitle after a chapter subtitle.

Colophon

A statement, usually on the last page of a book, describing elements of the book's production.

*Copyright

A book's copyright notice.

*Dedication

A book's dedication.

*Endnote Reference

A superscript reference number that refers to an endnote.

*Endnote Heading

A heading that introduces some endnotes, either at the end of a chapter or in a notes section at the back of the book. An example is "Notes to Chapter 12."

Endnote Subheading

A subheading between sections of endnotes.

*Endnote Text

The text of an endnote.

Epigraph

A saying or quotation that introduces a book ("Caveat lector").

Epigraph Source

The source of an epigraph, usually someone's name.

*Folio

A book's page number.

*Footnote Reference

A superscript reference number that refers to a footnote.

*Footnote Text

The text of a footnote.

Glossary Subhead

A subheading in a glossary.

Glossary Text

The text of a glossary entry.

*Heading 1,Part Title

Heading for a major section of a book. Using this level for part titles makes it possible to browse a book's sections in Microsoft Word's Outline View or Document Map.

*Heading 2,Chapter Title

Heading for a chapter title. Using this level for chapter titles makes it possible to browse a book's chapters in Microsoft Word's Outline View or Document Map.

*Heading 3,Subhead A

Subheading level A.

Heading 4,Subhead B

Subheading level B.

Heading 5,Subhead C

Subheading level C.

Heading 6,Subhead D

Subheading level D.

Heading 7,Subhead E

Subheading level E.

Heading 8,Subhead F

Subheading level F.

Heading 9,Subhead G

Subheading level G.

*Index 1 (Subject)

Text of an entry in a subject index.

Index 2 (Scripture)

Text of an entry in a scripture index.

Index 3 (Custom)

Text of an entry in some other kind of index.

Index Subhead

Subheading indicating a grouping of index entries. For example, an index to a biography of Mark Twain might include such subheadings as "Mark Twain, early life of" and "Mark Twain, writings of."

Jacket Blurb Book

Text of marketing copy (blurb) on a book jacket.

Jacket Blurb Author

Text of "about the author" copy on a book jacket.

Jacket Continued

Line of text explaining that the jacket blurb is continued on the back flap.

Letter Date

Date of a letter quoted in the text of a book ("June 10, 1900").

Letter Place

Place of a letter ("Boston").

Letter Salutation

Salutation of a letter ("Dear Ella").

Letter First

First paragraph of a letter.

Letter Middle

Middle paragraph of a letter. There may be more than one of these.

Letter Last

Last paragraph of a letter.

Letter Signature

Signature of the person writing a letter ("Your affectionate husband, William").

List

An item in a "list" consisting of a single item.

*List First

The first item in a list of items.

*List Middle

A middle item in a list of items. There may be more than one of these.

*List Last

The last item in a list of items.

*List Bullet

An item in a bulleted "list" consisting of a single item.

*List Bullet First

The first item in a list of bulleted items.

*List Bullet Middle

A middle item in a list of bulleted items. There may be more than one of these.

*List Bullet Last

The last item in a list of bulleted items.

List Number

An item in a numbered "list" consisting of a single item.

*List Number First

The first item in a list of numbered items.

*List Number Middle

A middle item in a list of numbered items. There may be more than one of these.

*List Number Last

The last item in a list of numbered items.

*Normal,Text 1

The normal text level of the body of a book.

*Normal Text 1 First

The first paragraph in a chapter or following a subheading. Used when the paragraph requires special formatting, such as extra leading.

*Normal Text 1 NI

Normal text, not indented. Usually used after a block quotation when the subject of the paragraph has not changed.

Normal Text 2

The second text level of the body of a book. Usually used to designate long passages from a second author.

Normal Text 2 First

The first paragraph in a chapter or following a subheading in a second text level. Used when the paragraph requires special formatting, such as extra leading.

Normal Text 2 NI

Second text level, not indented. Usually used after a block quotation when the subject of the paragraph has not changed.

Normal Text 3

The third text level of the body of a book. Usually used to designate long passages from a third author.

Normal Text 3 First

The first paragraph in a chapter or following a subheading in a third text level. Used when the paragraph requires special formatting, such as extra leading.

Normal Text 3 NI

Third text level, not indented. Usually used after a block quotation when the subject of the paragraph has not changed.

Note Text

The text of an "author's note" at the end of a book or chapter; not to be confused with endnote or footnote text.

Note Subhead

A subheading in a note.

Note Subsubhead

A subsubheading in a note.

*Part Number

The number of a major section of a book. See "Heading 1,Part Title."

Part Quote

A quotation at the beginning of a section.

Part Quote Source

A citation for a part quotation. This is usually someone's name.

Part Subsubtitle

A subtitle after a part title (Heading 1, Part Title).

Part Subtitle

A subtitle after a part subtitle.

Poem

A single line of poetry ("April is the cruelest month").

Poem Heading

Heading before a poem; usually the poem's title ("The Waste Land").

Poem Subhead

Subheading between stanzas of a poem ("What the Thunder Said").

*Poem First

First line of a poem (possibly indented).

*Poem First NI

First line of a poem (possibly not indented).

*Poem Start

Starting line of any poetry stanza but the first (possibly indented).

*Poem Start NI

Starting line of any poetry stanza but the first (possibly not indented).

*Poem Middle

Middle line of any poetry stanza (possibly indented). The stanza may include more than one of these.

*Poem Middle NI

Middle line of any poetry stanza (possibly not indented). The stanza may include more than one of these.

*Poem End

Ending line of any poetry stanza but the last (possibly indented).

*Poem End NI

Ending line of any poetry stanza but the last (possibly not indented).

*Poem Last

Last line of a poem (possibly indented).

*Poem Last NI

Last line of a poem (possibly not indented).

Poem Source

Citation following a poem (usually someone's name).

Pull Quote

A quotation set apart from the body text for emphasis.

Running Head First

First running head in a chapter, where such a running head needs different formatting from the other running heads (it may be centered, for example, while the others are left- and right-justified).

*Running Head Even

Running head on a left-hand (verso), even-numbered page.

*Running Head Odd

Running head on a right-hand (recto), odd-numbered page.

Sidebar Text

Text in a separate text box used as a direction, additional information, or tip.

Sidebar Head

Heading for sidebar text.

Table Heading

Heading that introduces a table.

Table Subhead

Subheading in a table.

Table Subsubhead

Subsubheading in a table.

Table Text

Text of a table.

_________________________________________

RESOURCES

Want to look at many more styles and templates? Check out the Microsoft Office Templates Gallery:

http://officeupdate.microsoft.com/templategallery/

Also, don't forget that Microsoft Word comes with a variety of useful templates. To see what these are:

1. Click "File."

2. Click "New."

3. Click the various tabs ("Publications," "Reports," etc.).

In the early days of printing, the "source" for the words on a printed page was the metal type used in the press. Once the pages had been printed, the type was removed from the printing forms and resorted into bins, completely destroying the source text. Producing a new edition of the book meant setting, proofreading, and correcting the type all over again--an enormous investment of time and money.

Too often people still do essentially the same thing today, even though we now have the technology (and the necessity!) to preserve source text (which is now electronic) and create new editions from it in a variety of forms:

* Printed books.

* Web pages.

* Electronic reference libraries.

* PDF (Adobe Acrobat) documents.

* Palm and PocketPC documents.

* Dedicated e-book reader documents.

And so on.

FORM FOLLOWS FUNCTION

Because people often need to produce a document (or parts of a document) in a variety of forms, a document's structure is far more important than its appearance--and in fact, its appearance should be derived from its structure. This is true because a document's appearance will change depending on the form in which it is presented. For example, a document presented on the printed page may look very different from the same document presented on a Web site.

In traditional typesetting, a chapter heading might be designed and typeset as 24-point Palatino. However beautiful that may be, it gives us no clue that the type is a chapter heading--information that would be crucial on a Web page or in an electronic reference library, where chapter headings might be used for linking, navigation, and so on. In other words, the heading's *function* is much more important than its *form.* Even in a particular printed book, if one chapter heading is set in 24-point Palatino, *all* of the book's chapter headings should be set in 24-point Palatino, because that signals the reader that any type so displayed *is,* in fact, a chapter heading. In type design, as in all other kinds of design, form should *follow* function.

Now consider what would happen if you had to put 300 different books together for an electronic reference library or Web site and needed to display all of the chapter headings for navigational purposes in a single table of contents. If chapter headings were electronically marked *as* chapter headings, it would be a piece of cake. If not, it would be a nightmare.

That's why it's no longer adequate to simply set type as 24-point Palatino. Instead, the type's *function* needs to be designated in a consistent, standardized way. Fortunately, that is not hard to do. In Microsoft Word, it's done with styles.

USING STYLES

Paragraph styles are a way to specify the function of a block of type and then assign a form (the type's appearance) to that function. As an example, consider the subheading above, "Using Styles." In a book, it might be formatted with a paragraph style named Heading 3, designating the line as a subheading. Heading 3 might format the line as 16-point Verdana type. However, it would be easy to redefine Heading 3 as 28-point Garamond, which would completely change its look. Nevertheless, it would *still* be styled as Heading 3--a subhead--and that can be useful in many ways.

For one thing, it would allow you to *change your mind* about a document's appearance. Let's say you've directly formatted (without styles) all of your main headings--102 of them, to be exact--as 24-point Arial, but the managing editor now thinks they should be bigger--28 points instead of 24. Let's also say you've used 24-point Arial elsewhere in your document, so you can't just find and replace the formatting you need to change. What does that mean? It means you now have the painful task of selecting and reformatting every single one of those 102 headings--unless, of course, you've used styles, in which case you can adjust the heading style with a few clicks of the mouse, *automatically* changing all 102 headings at once.

Using styles has other advantages, too:

* You can easily find one style and replace it with another. This is much simpler than having to search for directly applied formatting, such as 24-point Arial bold no indent.

* You can see and change the structure of your document in Outline view and Document Map.

* You can use the styles to automatically generate (or--after the author has added a new chapter--regenerate) a table of contents.

* You can use the styles to create automatic headers, footers, and cross-references.

If you're not using styles, you're spending a lot more time on formatting than you need to, and you're missing much of the power of Microsoft Word. In addition, you're making it difficult to reuse electronic text for other purposes--something we will all increasingly need to do.

STANDARD STYLE LIST

Because of this problem, you should consider marking type levels using a standard list of styles that will work well in your publishing environment. That doesn't mean every publication needs to *look* the same, since designers can *define* the styles any way they want. It does mean:

* Every publication should use styles from a standard list.

* No other styles should be used. In other words, don't just make up new ones as you go along. If you *need* a new one for a certain function not covered by the standard list, consult with others in your organization (such as typesetters and designers) so that everyone can be consistent.

* Styles should be used consistently from document to document. For example, you might always have Heading 1 be a part title, no matter what publication you are working on. Heading 2 could always be a chapter title. Heading 3 could always be a first-level subhead. And so on. If you then used the Heading 1 style for a chapter title or the Heading 2 style for a subhead, you would be at variance with the standard list, and that could cause problems in the future. Try not to think of a book as a single publication. Each book may eventually be part of a larger electronic *library* of books; if so, those books will need to be consistently produced.

* Text should not have directly applied formatting. For example, don't just select a heading and format it as 20-point Helvetica. Instead, apply the correct style for that heading and then *define* the style as 20-point Helvetica. In the short run, this may be a pain. In the long run, it will save enormous amounts of time, money, and frustration.

Stand by; next week I'll share my standard list of styles.

_________________________________________

READERS WRITE

David O. Taber wrote:

I'm looking for a MSWord add-in that supplements the spell/grammar checker functionality, to add extra rules of style. The idea is to catch hackneyed/overused words, expressions, or constructions automatically. For example, it would be cool to automatically flag the passive voice, incorrect capitalization, split infinitives. The usage mode is for a writer (me) to copy edit his own work for his own peculiar foibles.

I responded:

You might be interested in our MegaReplacer program, which allows you to customize your own list of such things. It also comes with some (free) lists of common corrections. You can learn more here:

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

In addition, you might want to make an "exclude dictionary" to take care of such things. You can learn more here:

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

Word's grammar checker will, to some extent, check passive voice, incorrect capitalization, and split infinitives, as well as overused words, etc. You may already know this, but you can set many such options under Tools/Options/Spelling & Grammar/Settings.

If those options aren't enough, you might be interested in Grammar Expert Plus, which looks more sophisticated than Microsoft's offering. You can learn more here:

http://www.wintertree-software.com/app/gramxp/index.html

Thanks to David for his message.

_________________________________________

RESOURCES

You'll find helpful tutorials on using styles at the following places:

Microsoft Word Legal User's Guide

http://officeupdate.microsoft.com/legal/styles.asp

Computer Tutor of San Francisco

http://www.geocities.com/w2css/styles/

Charles Kenyon's ADD Balance site

http://www.addbalance.com/usersguide/styles.htm

If you've been reading Editorium Update for a while, you know about wildcard searches and some of the neat things you can do with them. If you don't know about them, you can learn by reading these past issues of the newsletter:

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

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

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

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

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

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

Even though I use wildcard searches all the time, I don't do a very good job of saving my wildcard entries so I can use them again. But that's going to change when I make my wildcard dictionary. The dictionary will include entries in the following format:

* A description of what the Find and Replace wildcard strings do.

* The wildcard Find and Replace strings themselves.

* Some keywords I can search for if I'm looking for wildcard strings for a certain purpose.

* Before-and-after examples of what the wildcard strings do.

* Other comments.

Here's an example, with a wildcard string you may be able to use:

DESCRIPTION: Find parenthetical publishing information in source citations and replace it with nothing to help in changing citations to short form.

FIND WHAT: ([A-z ,.]@:[!)]@[0-9]{4})

RELACE WITH: [nothing]

KEY WORDS: publishing information, source, citation, footnotes, endnotes, books, parentheses, long, short, delete

BEFORE: Jack M. Lyon, Total Word Domination (Edina, Minn.: PocketPCPress, 2001), p. 237.

AFTER: Jack M. Lyon, Total Word Domination, p. 237.

COMMENTS: Won't find or delete other parenthetical text. *Note that the Find string includes a space in front of it, and that space is necessary.*

I'll save this kind of information for all of my wildcard strings henceforth and forever. Maybe you'd like to do something similar with yours.

I'll tell you what: If you'll send me your favorite wildcard strings with brief descriptions of what they do, I'll compile them into one big dictionary and publish it in a future issue of the newsletter for all to share. Please send your entries here:

mailto:editor [at symbol] editorium.com

If you don't have any, it's time to read those newsletter articles I mentioned above. You'll be glad you did!

_________________________________________

READERS WRITE

Continuing our Dvorak keyboard discussion, Rich Shattenberg wrote:

If you can find an old copy of Mavis Beacon, version 5, it has instructions for the Dvorak keyboard. I tried to convert once a year ago but something happened along the way and I reverted back to the old Qwerty system. It may have helped me if I had been using an actual Dvorak keyboard instead of a Qwerty keyboard.

Thanks to Rich for the useful information.

_________________________________________

RESOURCES

About.com has a valuable list of free software and other resources for word processing and desktop publishing:

http://desktoppub.about.com/cs/freebiesmisc/