Outlook 2010, Windows 7 64, Exchange Server 2010, using iMap.

Hello, occasionally, 3 incidents in the past several months, we'll compose an email in Outlook, with the subject containing the same message, properly translated, in both English and French, as soon as the email is sent, all the French accents characters (letter "e" with grave and and acute accents as examples) in the message change into Mingliu type fonts.  This results in an embarrassing further reply to our French readers apologizing for the technical issue.  Resending the same email again, using the same steps (as remembered and repeated many times a week) doesn't repeat the issue.  These emails are sent to a large number of BCC recipients.

We have some recipients mention that instead of Mingliu font, they see squares / triangles.  I suspect these recipients are using non Windows computers.

The change in characters only takes place after the Send button is pressed, there is no visible indication or warning ahead of time that the French accented characters will change.

Below are examples of the original accented word and it's translated version (as it appears in an Outlook 2010 Win 7 recipient).

As you can see from the above examples, the change is not consistent, in that all "   " characters are changed to the same Mingliu font characters.

There is no other Language packs installed in Office other than Canadian English and French and there are no Add-Ins that others have identified as possible causes.

I understand renaming the normalemail.dotm to .old is an option which I'll try.  Though the big concern from the Executive is that this issue hits with no warning, and it can take away from the intended content, especially trying to figure out the missing / replace French Accent characters.

Look forward to your feedback and appreciate your replies.

Take care,

Hello,

I suggest we enable the pipeline tracking log and see if the emails have been modified by Exchange Server:

https://technet.microsoft.com/en-us/library/bb125018(v=exchg.150).aspx

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Appreciate the advice, but given the randomness of the problem, I wouldn't know when to evoke the pipeline tracking log and what to look for once it takes place.  

Unfortunately there hasn't been a reply that provides something to work with.

I look forward to further information from Microsoft as to why this happens in the first place.

Thanks,