File Format & Compatibility

How to Fix Arabic Text Appearing as Symbols in Excel Workbooks

Algirdas JasaitisAlgirdas Jasaitis Nov 2, 2026 871 views

Question details

The user needs to resolve an issue where Arabic text in generated Excel workbooks renders as unreadable symbols instead of the correct characters.

How to Fix Arabic Text Appearing as Symbols in Excel Workbooks
Product
Microsoft Excel, Oracle WebLogic
Device & OS
not provided
Scenario
Opening an Excel workbook exported or generated from a web application containing Arabic text.
Observed behavior
Arabic characters display as incorrect symbols or gibberish, even when the Windows system locale is set to Arabic.
Before you start

Ensure that your system has Arabic language support installed and that standard Arabic Unicode fonts, such as Arial or Tahoma, are available on your device.

Solution 1Recommended

Isolate Font and Rendering Issues

Determine if the issue stems from the generated file's encoding or your local Excel font settings.

Often, files generated by third-party applications lack the correct font metadata. This solution helps isolate whether the problem is the file itself or your local Excel environment.

1
Test local Arabic input

Open a new, blank Excel workbook and type Arabic characters directly into any cell to confirm your local Excel application can render Arabic properly.

2
Test via Excel for the Web

Upload the generated file to your OneDrive account and open it in Excel for the Web. Cloud rendering handles fonts differently and can often bypass local application glitches.

3
Apply an Arabic Unicode font

In the desktop Excel app, highlight the cells containing the symbols, navigate to the Home tab, and select a recognized Arabic-supported font like Arial or Times New Roman from the Font dropdown menu.

Isolate Font and Rendering Issues
Check Application Settings: If typing Arabic locally works but the generated file remains garbled, the Oracle WebLogic application is likely exporting the file with an incorrect text encoding (such as ANSI instead of UTF-8).
Handle Multi-Language Excel Files with Ease

Easily Open and Edit Arabic Excel Files with WPS Office

WPS Office provides robust multi-language support and excellent format compatibility, automatically recognizing proper file encodings to prevent text from turning into unreadable symbols.

  1. 1. Install WPS Office: Download and install WPS Office for free from the official WPS website.
  2. 2. Open the generated workbook: Launch WPS Spreadsheets, click the 'Open' button on the left panel, and browse to select your generated Excel file.
  3. 3. Verify Text Display: WPS will automatically apply the most suitable encoding and font settings to display the Arabic text perfectly without manual adjustments.
Fully compatible with Microsoft Office formats, including .xlsx, .xls, and .csv.Excellent out-of-the-box support for Arabic and other right-to-left languages.Smart encoding detection prevents garbled text when opening generated files.Lightweight and free software that processes large generated files quickly.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Arabic text show as question marks or symbols in Excel?

This typically occurs when an external application exports the file using a legacy text encoding (like ANSI) instead of a universal standard like UTF-8. Excel fails to interpret the characters properly, replacing them with symbols or gibberish.

How can I permanently change the encoding of an exported Excel file?

If the file is a CSV or plain text format, you can right-click the file, open it with Notepad, click File > Save As, and select 'UTF-8' from the Encoding dropdown menu before saving. You can then open this new file normally in Excel.

Will changing my Windows system locale to Arabic fix the symbols?

Changing the system locale (Administrative language settings) to Arabic helps non-Unicode programs display Arabic correctly. However, if the source application (like WebLogic) explicitly generated the file with broken internal encoding, changing the Windows locale alone may not resolve the issue.