MS Word cannot convert wingdings back to their original font. Outlook can !!!

The last 3 lines of the attached file, (“Joe.doc”) have the word “Joe”. But the lines look weird because their font was changed to Wingdings.

Using Word 2010 thru 2016 I selected the entire document then use ctrl spacebar to convert to times new roman.  The words converted to 3 boxes ().  

I fixed it by copying the text word to Outlook then back to word.  Outlook’s ctrl spacebar worked properly.

Does anybody know why Word in “native” mode fails?


P.S.  If you try this yourself do the following
1 open new word file > type "joe" > convert font to Wingdings
2 close the file > reopen it
3 ctrl A > ctrl space bar.

If you skip step 2, Word will appear to work properly.
Who is Participating?
Jim RiddlesConnect With a Mentor Prepress/OMS SpecialistCommented:
Here is a long-winded explanation for Word 2002, which apparently still applies: WD2002: Symbol Characters Are Changed to Box Characters
rberkeConsultantAuthor Commented:
Typical MS crud.  Converting from times new roman to wingdings works, but converting from wingdings back to times new roman does not.

I reviewed the link you provided and found it to be incomplete.  Mainly MS should simply come out a say "this is a bug that MS does not care to fix".

Instead the link obfuscates and implies that Unicode technicalities cause the problem. Sure Unicode can be complicated, but somehow Excel, Power Point, Publisher, Visio, and Outlook all work fine, it is only Word that screws up.

Even worse, Word is the engine  that Outlook invokes for editing E-Mail bodies.  But when running under Outlook, Word DOES NOT HAVE THE WEIRD BEHAVIOR. So, Word is inconsistent with itself !

The article should also include a better workaround that does not require VBA:  1) Open Outlook and create a new email.  2) copy the contents of your Word file with wingdings to the clipboard. 3) Paste it into the Outlook email.  4) Use find and replace to change all occurrences of Wingdings to Times New Roman.  5) copy the text back to you word document.

I posted that as a suggestion using the article's feedback button, but I would be shocked if MS pays any attention.
rberkeConsultantAuthor Commented:
Thanks for finding the article about this MS Word problem.  Hard to believe it has been around since Word 97 and still has not been fixed in Word 2016.  Microsoft sometimes takes a long time to fix a bug but 20 years is really exceptional.
Jim RiddlesPrepress/OMS SpecialistCommented:
I had the exact same thoughts in regards to the fact that other MS products do not suffer from the same affliction.  It is inconceivable that this is still an issue in MS Word after all this time.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.