View Single Post
 
Old 07-23-2020, 04:55 PM
Guessed's Avatar
Guessed Guessed is offline Windows 10 Office 2016
Expert
 
Join Date: Mar 2010
Location: Canberra/Melbourne Australia
Posts: 3,994
Guessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant futureGuessed has a brilliant future
Default

You are right - I thought I saw in your doc that body_base was based on Normal but it is actually based on no style. Still, in my mind, this is just an additional level of complexity that adds no value because you already understand how styles are chained together. You say you can tweak your base style to change all of the related styles. Yep Equally you could do the same if your children styles were based on Normal. As long as you understand style hierarchies, you can configure your styles to best suit your work patterns. But you don't NEED to add artificial complexity.

I wouldn't expect that upgrading Word is likely to resolve the issue you are seeing. Certainly, when I looked at your document in Word 2016 I could see the issue that you put in it so using a newer version of Word is not resolving the phantom markup already in the document. It is possible that a newer version wouldn't INTRODUCE the problem while you are making tracked edits but I would be surprised if was different to earlier versions of Word.

In my experience, the evolution of Word's underlying behaviour is extremely minimal. Each newer version of Word changes the graphical user interface in large or small increments but the underlying functionality rarely changes.

I just thought of a simple change your could make to your document to mask this bug and hide the fact it is still there. What you are seeing is the text colour of Accent 6 is being added to the text. You notice this because this colour is NOT black - so the simple fix is to change the Accent 6 colour so it is Black. This change will not stop the bug but it will make it so no one notices it.

At some stage, AFTER your revisions are accepted/rejected and you want to do a quick cleanup to remove the remnants of this bug - you can run the command to remove all local font formatting WHILST retaining character formatting.

There are two commands to remove font formatting. The obvious Font Reset (Ctrl-D) command also gets rid of character styles so you need to avoid that one if your document intentionally uses character styles. The non-obvious vba command that retains the character styling but gets rid of other font changes is
Code:
Selection.ClearCharacterDirectFormatting
__________________
Andrew Lockton
Chrysalis Design, Melbourne Australia
Reply With Quote