by Jack Lyon<\/strong><\/em><\/p>\n During my editing career, I've often run into problems with footnotes and endnotes in Microsoft Word. Many authors have no clue about how notes are meant to work, and Microsoft certainly hasn't made it obvious. In fact, they've made it easy to mess notes up beyond repair.<\/p>\n One mistake authors make is to insert extraneous carriage returns before or after a note. Why? Because they don't like the positioning of the note on the page, which they're trying to make \"pretty,\" not understanding the problems that will cause in editing and typesetting.<\/p>\n You can try to remove the extraneous returns like this:<\/p>\n 1. Click View > Draft. Your cursor should now be in the Notes pane.<\/p>\n 3. Click Home > Replace. ^p^p<\/p>\n 5. In the \"Replace With\" box, enter one paragraph code:<\/p>\n ^p<\/p>\n \u00a06. Click the \"Replace All\" button.<\/p>\n Word will replace some of the double returns, but not all of them. And if you try to delete some of the remaining returns, you'll get an error message:<\/p>\n \"This is not a valid action for footnotes.\"<\/p><\/blockquote>\n What's going on there is that not all carriage returns are created equal. Some of the returns are \"special\" note returns, and the only way to delete them is to delete the note itself back in the text.<\/p>\n The solution? A macro, of course. But a macro with a twist. As we've seen, the macro can't just find double returns and replace them with a single return. And trying to delete extra returns results in an error. So let's use that error!<\/p>\n Before running the macro, you must be in Draft view, with your cursor at the top of the Notes pane. (How to get there is explained above.)<\/p>\n In the macro, you'll see a couple of \"comments,\" which are explanations or instructions intended for the person reading the code. Comments are preceded by a single quotation mark ('), which tells the macro to ignore the rest of the text on that line. For example, the first comment in the macro reads:<\/p>\n 'To clean returns in endnotes rather than footnotes, change \".Footnotes\" to \".Endnotes\" in the following line:<\/p><\/blockquote>\n And now, here's the macro:<\/p>\n Sub CleanReturnsInNotes() .Text = \"^p^p\" End With Selection.MoveLeft Wend ErrorCount = ErrorCount + 1 TheEnd: Let's look at some of those lines.<\/p>\n NoteCount = ActiveDocument.Footnotes.Count<\/p>\n NoteCount is a variable; that is, it's a container that can hold a numerical value\u2014in this case, the number of footnotes in the document. We get that value with the VBA command ActiveDocument.Footnotes.Count.<\/p>\n Selection.Find.ClearFormatting Just to be safe, these lines clear any formatting that might already be applied to the \"Find What\" and \"Replace With\" boxes in Word's find and replace feature.<\/p>\n The following lines, from<\/p>\n With Selection.Find<\/p>\n down to<\/p>\n Selection.Find.Execute<\/p>\n simply find any instances of double paragraph returns. The replacement text is set to nothing, as we're not trying to replace those returns with anything:<\/p>\n \u00a0.Replacement.Text = \"\"<\/p>\n Instead, we're going to try to delete the second return, which (unless the notes are really messed up) is a regular return rather than a special note return:<\/p>\n \u00a0Selection.MoveRight If it's a special note return, then trying to delete it will cause an error, and the macro will execute this line\u2014<\/p>\n On Error GoTo TrapTheError<\/p>\n \u2014which sends the macro to this line:<\/p>\n TrapTheError:<\/p>\n Here's what happens next:<\/p>\n ErrorCount = ErrorCount + 1<\/p>\n Using the variable ErrorCount, we count the number of errors, adding 1 each time we find one. (ErrorCount is initially empty, or zero.)<\/p>\n Selection.MoveRight We move right and delete the next return.<\/p>\n \u00a0If ErrorCount < NoteCount Then Resume Next<\/p>\n If the number of errors is less than the number of notes, we're not through yet, as one of the remaining notes may still have a bad return next to it. So, we tell the macro to Resume operation at the next command after the error occurred. That command is:<\/p>\n Selection.Find.Execute<\/p>\n In other words, Word looks for the next occurrence of a double return. And this construction\u2014<\/p>\n While Selection.Find.Found<\/p>\n Selection.MoveLeft Wend<\/p>\n \u2014ensures that it will keep looking as long as (While) double returns are found. (\"Wend\" is short for \"While End\"\u2014it marks the end of the While construction.)<\/p>\n GoTo TheEnd<\/p>\n When no more double returns are found, this line is executed. It exists simply to avoid executing the error trap (TrapTheError and the following lines) after the macro is finished, at which point<\/p>\n TheEnd:<\/p>\n marks the end of the whole operation.<\/p>\n I hope this explanation has helped you understand better how macros work, and in particular how you can actually use Word errors to force Word to do what you want it to do\u2014something that gives me great pleasure.<\/p>\n Even if you don't understand everything that's going on in this macro, you can still use it to clean up extraneous returns in notes\u2014something that should make your editorial life a little bit easier.<\/p>\n Jack Lyon (<\/em>editor@editorium.com<\/em><\/a>)\u00a0owns and operates the <\/em>Editorium<\/em><\/a>, which provides macros and information to help editors and publishers do mundane tasks quickly and efficiently. He is the author of <\/em>Microsoft Word for Publishing Professionals<\/a> and of <\/em>Macro Cookbook for Microsoft Word<\/a>. Both books will help you learn more about macros and how to use them.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" One mistake authors make is to insert extraneous carriage returns before or after a note. Why? Because they don’t like the positioning of the note on the page, which they’re trying to make “pretty,” not understanding the problems that will cause in editing and typesetting.<\/p>\n<\/a>","protected":false},"author":9,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[77,256,22,67,409],"tags":[267,446,447],"class_list":{"0":"post-4160","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-computers-and-software","7":"category-contributor-article","8":"category-editorial-matters","9":"category-guest-article","10":"category-lyonizing-word","11":"tag-jack-lyon","12":"tag-macros","13":"tag-removing-returns-in-notes","14":"h-entry","15":"hentry"},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p3gfno-156","_links":{"self":[{"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/posts\/4160","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/comments?post=4160"}],"version-history":[{"count":1,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/posts\/4160\/revisions"}],"predecessor-version":[{"id":5990,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/posts\/4160\/revisions\/5990"}],"wp:attachment":[{"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/media?parent=4160"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/categories?post=4160"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/tags?post=4160"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n2. Click References > Show Notes.<\/p>\n
\n4. In the \"Find What\" box, enter two paragraph codes:<\/p>\n
\n'To clean returns in endnotes rather than footnotes, change \".Footnotes\" to \".Endnotes\" in the following line:
\nNoteCount = ActiveDocument.Footnotes.Count
\nSelection.Find.ClearFormatting
\nSelection.Find.Replacement.ClearFormatting
\nWith Selection.Find<\/p>\n
\n.Replacement.Text = \"\"
\n.Forward = True
\n.Wrap = wdFindContinue
\n.Format = False
\n.MatchCase = False
\n.MatchWholeWord = False
\n.MatchAllWordForms = False
\n.MatchSoundsLike = False
\n.MatchWildcards = False<\/p>\n
\nSelection.Find.Execute
\nOn Error GoTo TrapTheError
\nWhile Selection.Find.Found<\/p>\n
\n'The following line may trigger an error!
\nSelection.Delete
\nSelection.Find.Execute<\/p>\n
\nGoTo TheEnd
\nTrapTheError:<\/p>\n
\nSelection.MoveRight
\nSelection.Delete
\nIf ErrorCount < NoteCount Then Resume Next<\/p>\n
\nEnd Sub<\/p>\n
\nSelection.Find.Replacement.ClearFormatting<\/p>\n
\nSelection.Delete<\/p>\n
\nSelection.Delete<\/p>\n
\n'The following line may trigger an error!
\nSelection.Delete
\nSelection.Find.Execute<\/p>\n