T Lubin: Your problem is different than the original post. Please start a new thread, including your operating system and version of Word.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am on a 2020 Macbook Air running Big Sur 11.7.1, and Microsoft Office for Mac 16.77. In the last year or so, many (but not all) unicode Devanagari fonts has stopped functioning properly in Office (e.g. Word, Outlook). Conjunct glyphs are decomposed with virama ("vowel-killer") under each part of the consonant cluster. This is happening with many commonly used Devanagari fonts including Arial Unicode, Devanagari MT, Sanskrit 2020, Mangal, and others (though a few still seem to work).
Even if I copy Devanagari text that is properly displayed in a non-Microsoft program such as TextEdit or LibreOffice, when I paste it into Word or Outlook, it is displayed incorrectly.
This is a major step backward in functionality of Microsoft products with Unicode. What is the problem. Can it be fixed?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
T Lubin: Your problem is different than the original post. Please start a new thread, including your operating system and version of Word.
Actually the problem T. Lubin describes is exactly the problem I described my original post. I am using Word 2019 (16.76.1) with Mac OS 12.6.8 (Monterey).
Yes, and I am on Mac OS 11.7.1 using Word for Mac 16.77. The problem affects Outlook too. I have posted this question separately at
Split from this thread.
I have the same problem but with multiple Devanagari fonts, both in Word and in Outlook. They used to work fine, but now conjunct glyphs are all decomposed with the use of virama. This is a major step backward for Microsoft. (BTW, everything still works fine in LibreOffice!)
This is a major step backward in functionality of Microsoft products with Unicode. What is the problem. Can it be fixed?
Not a major step backward but perhaps a step forward.
Do these happen to be PostScript Type 1 fonts? If so, PostScript Type 1 was deprecated by Adobe earlier this year & is no longer supported by Microsoft. Per the Release Notes for the 16.76 Update:
Deprecation of PostScript Type 1 fonts: Support for PostScript Type 1 fonts is ending on the Microsoft 365 apps for macOS.