Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

Arabic font is not displayed properly

  • 3 yanıt
  • 23 kişi bu sorunu yaşıyor
  • 141 gösterim
  • Son yanıtı yazan: cor-el
  • Arşivlendi

hkBattousai
hkBattousai

While displaying Arabic text, Firefox is adding space between each Arabic letter, which is quite undesirable and is actually messing up the text.

In Firefox (adding space between letters): http://img64.imageshack.us/img64/7442/firefoxhx.png

In Chrome (properly displaying Arabic text): http://img196.imageshack.us/img196/8056/chromeu.png

I want to solve this problem. What should I do for it? Is there any setting I have to change, or should I install another Arabic font (if so, how?)?

While displaying Arabic text, Firefox is adding space between each Arabic letter, which is quite undesirable and is actually messing up the text. In Firefox (adding space between letters): http://img64.imageshack.us/img64/7442/firefoxhx.png In Chrome (properly displaying Arabic text): http://img196.imageshack.us/img196/8056/chromeu.png I want to solve this problem. What should I do for it? Is there any setting I have to change, or should I install another Arabic font (if so, how?)?

hkBattousai tarafından tarihinde düzenlendi

Tüm Yanıtlar (3)

cor-el
cor-el
  • Top 25 Contributor
  • Moderator

Sounds like this bug:

  • Bug 635639 - Vowels are not rendered correctly in some Persian/Arabic/Hebrew fonts
hkBattousai
hkBattousai Sorunun sahibi

Status of the "'BUG 635639 is "'RESOLVED FIXED. So that bug must had been something different.

cor-el
cor-el
  • Top 25 Contributor
  • Moderator

It will be fixed in a future Firefox version, but isn't fixed yet in the current Firefox 4 release. There will be an update of Firefox 4 later this month (Apr 26).
Judging from comment comment 49 I assume that the patch has been ported to the Firefox 4 branch, so you may be lucky: