{"id":6416,"date":"2022-10-25T16:36:07","date_gmt":"2022-10-25T22:36:07","guid":{"rendered":"https:\/\/editorium.com\/archive\/?p=6416"},"modified":"2022-11-11T11:29:43","modified_gmt":"2022-11-11T18:29:43","slug":"three-wildcard-secrets","status":"publish","type":"post","link":"https:\/\/editorium.com\/archive\/three-wildcard-secrets\/","title":{"rendered":"Three Wildcard Secrets"},"content":{"rendered":"<p>So, you\u2019ve been using wildcards with Microsoft Word\u2019s Find and Replace feature to save time and ensure consistency as you edit the plethora of freelance work that\u2019s bombarding your inbox. Excellent. But even if you\u2019re getting pretty good at using wildcards, there are actually a few secrets that even many experts don\u2019t know. Maybe you\u2019ll find them useful.<\/p>\n<h3>Secret #1<\/h3>\n<p>Using the wildcard range [A-z] to find any uppercase or lowercase letter will not find accented letters. Take, for example, the word r\u00e9sum\u00e9. [A-z] will find the r, s, u, and m in that word, but it will skip over the two occurrences of \u00e9. Go ahead, try it. I\u2019ll be here when you get back.<\/p>\n<p>If you actually want to skip over accented letters, [A-z] might come in handy sometime, but that will rarely be the case. To find all letters, both accented and unaccented, use the wildcard range [A-Za-z] instead. Also, as you might expect, [A-Z] finds both accented and unaccented capital letters, and [a-z] finds both accented and unaccented lowercase letters.<\/p>\n<p>Okay, so [A-z] skips over accented characters; that suggests the idea that we could use a variation on that range to find only accented characters. How? Add an exclamation mark at the beginning of the range, which tells Word to find any character except what is in the range. The modified range looks like this: [!A-z]. Again, using the word r\u00e9sum\u00e9, [!A-z] finds the two occurrences of \u00e9 but skips over r, s, u, and m. If you need to find accented characters, now you know how.<\/p>\n<h3>Secret #2<\/h3>\n<p>In a wildcard search, you can\u2019t search for Unicode characters using numeric codes (such as ^u945), but you can copy Unicode characters from a document and paste them into Word\u2019s Find box. You can even search for a range of Unicode characters. For example, the range [?-?] from the Greek alphabet (lowercase alpha through omega) finds every character in the Greek greeting ???? ???. You can see the range of characters in various languages by clicking Word\u2019s Insert tab and then the Symbol button on the ribbon:<\/p>\n<p>For example, here, in order, are some of the Cyrillic characters available in Word:<\/p>\n<p>If you need to find any (unspecified) Unicode character in a document, you can use this not range:<\/p>\n<p>[!^000-^255]<\/p>\n<p>That works because 127 is the upper limit on ASCII characters and 255 is the upper limit on ANSI characters. This wildcard string excludes them both, so anything it finds must be Unicode.<\/p>\n<h3>Secret #3<\/h3>\n<p>You can use the search code ^p to search for paragraph breaks in a regular search, but not with wildcards. If you try, Word will display an error message:<\/p>\n<p>So how do you search for paragraph breaks when using wildcards? Instead of ^p, use ^013. All well and good, but here\u2019s the real secret: In Word\u2019s Replace box, you must not use ^013; instead, use ^p. That\u2019s right:<\/p>\n<p>Find what: ^013<\/p>\n<p>Replace with: ^p<\/p>\n<p>Why? Because Word\u2019s paragraph breaks are not the same thing as an ANSI paragraph break (^013). Word stores all kinds of stuff in paragraph breaks (formatting, for example), and an ANSI break is just a character like any other. I\u2019ve occasionally had to work on documents that came from who-knows-where, and my usual wildcard searches wouldn\u2019t work. I finally realized that those documents were using ANSI paragraph breaks rather than Word\u2019s proprietary paragraph breaks. The solution? Once again:<\/p>\n<p>Find what: ^013<\/p>\n<p>Replace with: ^p<\/p>\n<p>After I replaced the ANSI breaks, my wildcard searches worked again.<\/p>\n<h3>Bonus Secret<\/h3>\n<p>Microsoft Word\u2019s wildcard search engine uses a modified version of what is widely known as RegEx\u2014short for \u201cregular expressions.\u201d RegEx is more powerful than Word\u2019s version of it, but if you\u2019re feeling geeky, you can actually use RegEx in Word\u2014not in Word\u2019s Find and Replace dialogs but in a macro. If you\u2019re interested, you can learn more here:<\/p>\n<p><a href=\"http:\/\/www.regular-expressions.info\/vb.html\">http:\/\/www.regular-expressions.info\/vb.html<\/a><\/p>\n<p>I hope you find these wildcard secrets useful. If you\u2019re just getting started with wildcards, please check out my in-depth book on the subject, Wildcard Cookbook for Microsoft Word (ISBN 978-1-4341-0398-7), available at Amazon, Barnes &amp; Noble, and other purveyors of fine technical literature.<\/p>\n","protected":false},"excerpt":{"rendered":"<a href=\"https:\/\/editorium.com\/archive\/three-wildcard-secrets\/\" rel=\"bookmark\" title=\"Permalink to Three Wildcard Secrets\"><p>So, you\u2019ve been using wildcards with Microsoft Word\u2019s Find and Replace feature to save time and ensure consistency as you edit the plethora of freelance work that\u2019s bombarding your inbox. Excellent. But even if you\u2019re getting pretty good at using wildcards, there are actually a few secrets that even many experts don\u2019t know. Maybe you\u2019ll [&hellip;]<\/p>\n<\/a>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","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":[19],"tags":[],"class_list":{"0":"post-6416","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-wildcards","7":"h-entry","8":"hentry"},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p3gfno-1Fu","_links":{"self":[{"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/posts\/6416","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\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/comments?post=6416"}],"version-history":[{"count":0,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/posts\/6416\/revisions"}],"wp:attachment":[{"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/media?parent=6416"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/categories?post=6416"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/editorium.com\/archive\/wp-json\/wp\/v2\/tags?post=6416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}