'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Persian Font Rendering Problems in Word for Mac
Question details
Users need to resolve an issue where Persian characters display incorrectly at the ends of words in Word for Mac after a recent software update.
- Product
- Microsoft Word for Mac
- Device & OS
- Mac OS
- Scenario
- Editing or viewing documents containing Persian text using B-series fonts after installing a Microsoft 365 update.
- Observed behavior
- Specific Persian characters render incorrectly and appear disconnected at the ends of words when using B Nazanin, B Zar, and other B-series fonts. Changing character spacing does not resolve the issue, and the bug does not appear in other Mac applications.
Ensure your Mac is connected to your Time Machine backup drive so you can access previous versions of your applications.
Restore an Earlier Version of Word Using Time Machine
Since the rendering issue is a bug introduced in a recent Microsoft 365 update, rolling back to the previous version of Word is the most effective solution.
This bug specifically affects the rendering engine in the updated version of Word for Mac. Reverting to the previous stable release will restore proper text shaping for complex scripts like Persian.
Open Finder on your Mac and navigate to the Applications folder where Microsoft Word is installed.
Click the Time Machine icon in your menu bar and select 'Enter Time Machine' to view your backups.
Use the timeline on the right side of the screen to go back to a date before the problematic Microsoft 365 update occurred.
Select the Microsoft Word application in the backup and click 'Restore' to replace the currently installed buggy version.
Switch to Alternative Arabic/Persian Fonts
If you cannot restore an older version of Word, temporarily changing your document font can bypass the rendering bug.
Try WPS Office for Seamless Persian Text Editing on Mac
If Microsoft Word updates continually disrupt your workflow, consider switching to WPS Office. It is a free, lightweight, and highly compatible alternative that offers a familiar UI, seamless migration, and flawless multi-language rendering without unexpected update bugs.
- 1. Download for Mac: Visit the official WPS Office website and download the free installation package for Mac.
- 2. Install the app: Open the downloaded file and drag the WPS Office icon into your Applications folder.
- 3. Open existing files: Launch WPS Office and directly open your existing .docx files to view your Persian text rendered perfectly.
Frequently Asked Questions
Will changing character spacing fix the disconnected Persian letters?
No, adjusting character spacing does not resolve this specific issue. The problem lies within the font rendering engine of the updated Word version, not the document's formatting settings.
Does this font rendering bug affect other Mac applications?
No, users report that B Nazanin, B Zar, and other B-series fonts continue to display perfectly in other Mac applications. The issue is strictly isolated to Microsoft Word for Mac following a specific update.
When will Microsoft fix the Persian font issue in Word for Mac?
Microsoft typically addresses rendering bugs in subsequent patch releases. Keeping your Microsoft AutoUpdate on manual allows you to monitor release notes and community forums before deciding to install the next update.
