Hindi unicode does not display correctly




5 years ago
5 years ago


(Reporter: hhaneji, Unassigned)


25 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)



(1 attachment)

551 bytes, text/html


5 years ago
Created attachment 806830 [details]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258

Steps to reproduce:

Open attached test.htm on firefox

Actual results:

Hindi by unicode are not correctly displayed on firefox. Microsoft IE and Google Chrome can display correctly. I did not confirm other language unicode.

Expected results:

Should be correctly displayed same as other browser.


5 years ago
Severity: normal → major
Component: General → General
Priority: -- → P1
Product: Core → Firefox
Version: 27 Branch → 25 Branch


5 years ago
Attachment #806830 - Attachment mime type: text/plain → text/html


5 years ago
Severity: major → normal
Component: General → Layout: Text
Priority: P1 → --
Product: Firefox → Core
These are combining marks; it doesn't generally make much sense to use them in isolation, without an appropriate base letter (or following a space / non-breaking space). Do they display correctly when used within actual text?

If you really want to display the marks in isolation, with a dotted-circle in place of the base letter (e.g. for a chart of Unicode characters), you should explicitly encode them as such, e.g. ◌॑. Do they display correctly when used in this way?

Comment 2

5 years ago
Hi Jonathan,
Thank you for your comment but would you please just open the attached test.htm by Microsoft IE or Google chrome? You can see the difference from the case of firefox.
I don't think that the content in the attached test.htm has wrong format. And I cannot understand what you want to say but the technically any unicode by such format like as ॑, ॒ and ॓ should be correctly converted to display the standardized characters on the browser like as Microsoft IE or Google chrome. Therefore, it is definitely clear that firefox has bug.
You need to log in before you can comment on or make changes to this bug.