VBA, Style names, Find-Replace Special Character Codes, and non-English versions of W

This post started off as a query, but I have since resolved most of the issues ... however ...

I have a collection of macros that are being used by a friend in the Netherlands who is using the Dutch version of Word on English language documents that are set to UK English. One of these routines sets text to the 'Normal' style (but retains all font attributes). The 'Normal' style is called 'Standaard' in the Dutch version. Word was saying that it didn't recognize the style 'Normal' even though most of the document is in this style - when you look at it in an English version of Word. I think I've fixed this by using wdStyleNormal in place of "Normal". Likewise for any other built-in style names.

There is another issue using the special characters in Find-Replace dialogues. For example, ^t for Tab is not recognized by the Dutch Word, and likewise other Dutch special characters. I have got around this by using the relevant decimal number. eg. ^9 or vbTab for tab, ^255 for non-breaking space, etc. But does anyone know how to handle ^f and ^e for endnotes and footnotes in VBA for all language versions of Word?

Need to change the title of this thread to "VBA, Style names, Find-Replace Special Character Codes, and non-English versions of Word"

https://support.office.com/en-us/art...rs=en-US&ad=US


NBS is ^160
Footnote is ^2
Endnotes seem to be only ^e

Thanks. Oddly, ^160 does not find hard spaces in my version of Word (EnglishUK, 2003), but ^255 does. I don't know what works with English versions of Word 2007, 2010, 2013, 2016, 365. But ^255 does not work with my friend's Dutch version (prob. 2010 or 2013), so I'll try ^160. I'm using the function below, and for English versions will stick with ^s, which seems to be universal to all English versions. I'll deal with other language versions if they crop up.

Code:

---

Function hs () As String
    If Application.LanguageSettings.LanguagePreferredForEditing(msoLanguageIDDutch) = True Then
        hS = "^160"            ' or whatever special character sequence is used in Dutch
    Else
        hS = "^s"
    End If
End Function

---

Depending on the context, use ^0160 or Chr(160) for a standard non-breaking space. There are other non-breaking space characters, too (e.g. Unicode 202F gives a Narrow No-Break Space).

Thanks. That does the trick!

Now here's strange thing. This bit of code works in Word 2003/2010/2013/2016 Office apps (English versions), but does not work in my friend's Dutch version, where the wildcard search string is rejected as an invalid search string. Likewise, using ([ ^s]){2,}

^s is the valid special character sequence for non-breaking space.

Code:

---

.Text = "([ ^0160]){2,}": .Replacement.Text = " ": .Forward = True: .Wrap = wdFindStop
        .MatchWildcards = True: .Execute replace:=wdReplaceAll

---

However, this bit of code works on both systems:

Code:

---

.Text = "^w": .Replacement.Text = " ": .Forward = True: .Wrap = wdFindStop
        .MatchWildcards = False: .Execute replace:=wdReplaceAll

---

Can anyone see why ([ ^0160]){2,} and ([ ^s]){2,} are treated as invalid strings in a Dutch version of Word 2010, but not in English versions?

In systems using non-Engish regional settings, one typically needs to replace the comma separator in the wildcard Find expression with a semi-colon. For example:
Find = [ ^0160]{2,}
becomes:
Find = [ ^0160]{2;}
PS: You don't need the parentheses.

Umm.... Thanks. Very interesting. Also, I think maybe it should be ([ ^0160]{2,}) not ([ ^0160]){2,}, although my version of Word accepts both. My English version of Word does not accept the ; in place of a , But yes, the parentheses are not required for this operation.

Hope this dialogue helps someone, somewhere, sometime ... It's certainly helped me!

Thanks for the help from the two Pauls. I'll mark the thread as solved.

Quote:

---

Originally Posted by johndavidson

I think maybe it should be ([ ^0160]{2,}) not ([ ^0160]){2,}, although my version of Word accepts both.

---

Where the closing parenthesis should be (when needed) depends on what you're using them for.