Arabic combining diacritical marks are rendered separately, not above or below the characters

RESOLVED WORKSFORME

Status

()

Core
Layout: Text
RESOLVED WORKSFORME
15 years ago
9 years ago

People

(Reporter: Roland Unger, Assigned: mkaply)

Tracking

Trunk
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(8 attachments, 1 obsolete attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/4.78 [en] (Win98; U)
Build Identifier: 2002101612

As a part of the Arabic Unicode plane, some combining diacritical marks (for 
instance Fatha, Kasra and so on) are defined. Mozilla does not render a 
combination, but two separate characters.

Reproducible: Always

Steps to Reproduce:
1.See attached test file.
2.
3.
(Reporter)

Comment 1

15 years ago
Created attachment 106212 [details]
HTML file with Arabic text and diacritical marks

UTF-8 coded test file containing an English title and three Arabic words
(shukran, kurrasa, mu'allim) with their diacritical marks.

Comment 2

15 years ago
This is because of Mozilla's severe limitations rendering Unicode. See bug
157967 for details.

Comment 3

14 years ago
This is a critical bug for proper Arabic - any further status and/or movement to
eradicate this problem (its been awhile since it was looked into) ?

Comment 4

14 years ago
This works fine in Windows.
The problem still in exists in Linux though.
I'll try to attach a screenshot using Linux and the latest nightly build.

Comment 5

14 years ago
Created attachment 132338 [details]
Screenshot in Windows showing display of Arabic diacritics fine

As you can see in the shot, I'm using a nightly build (20030924) and Windows
XP.

Comment 6

14 years ago
Created attachment 132341 [details]
A test case in RH9 using Mozilla 1.4

The first line has broken words on diacritics, but not the second line (where
there isn't a font specified!).

Comment 7

14 years ago
Created attachment 132342 [details]
A screenshot of the previous (test2.html) test page.

This is how it look on my RH9 machine. BTW, I have fonts-arabic RPM package
installed as well as ae_fonts.

Comment 8

14 years ago
Additional comment #5 says :

>Screenshot in Windows showing display of Arabic diacritics fine

This is *not* true on Windows 98 (either using Mozilla 1.4, 1.5RC2 or NS 7.02).
(Reporter)

Comment 9

14 years ago
Created attachment 132874 [details]
HTML file with Arabic text and diacritical marks - extended -

UTF-8 coded test file containing an English title and three Arabic words
(shukran, kurrasa, mu'allim) with their diacritical marks. The text is
written twice; the second time with the font Traditional Arabic to test
OpenFont properties
(Reporter)

Updated

14 years ago
Attachment #106212 - Attachment is obsolete: true
(Reporter)

Comment 10

14 years ago
Created attachment 132876 [details]
A screenshot of the previous (test.html) test page - Win 98 - M1.5 RC2 

In case of Windows 98, Arabic combining diacritical marks are rendered
separately.
Arabic Support installed. Correct working with IE 6 and MS Word
(Reporter)

Comment 11

14 years ago
Created attachment 132877 [details]
A screenshot of the previous (test.html) test page - Win 2000 - M1.5 RC2

In case of Windows 2000 and Mozilla 1.5 RC2 it works correctly.

Comment 12

13 years ago
*** Bug 181669 has been marked as a duplicate of this bug. ***
*** Bug 257101 has been marked as a duplicate of this bug. ***

Comment 14

13 years ago
Created attachment 158963 [details]
Screenshot of unicode UTF-8 vietnamese characters

Attached screenshot shows combining diacriticals not displaying correctly in a
utf-8-encoded Vietnamese file. Same file displays correctly in Safari.

Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913
Firefox/0.10

Comment 15

12 years ago
Created attachment 193952 [details]
Both bad and good rendering
*** Bug 306068 has been marked as a duplicate of this bug. ***
Please note that two of the recent dupes were for non en-US (French and Czech)
installations on Windows 2000/XP.
Changing OS to "All".
OS: Windows 98 → All

Comment 18

12 years ago
(In reply to comment #17)
> Please note that two of the recent dupes were for non en-US (French and Czech)
> installations on Windows 2000/XP.

On Windows 2k/XP, that should work fine. It doesn't work there (in cases of two
dupes) because they didn't turn on 'complex script' support in Control Panel |
Regional&Lang. setting. MS IE just works even without it (because MS IE directly
uses Uniscribe APIs), but Firefox does need that to be turned on. (see bug 218887)

> Changing OS to "All".

Well, this bug on its own is all but useless. It's just a dupe of several
complex script rendering bugs on different platforms. 

Comment 19

11 years ago
Mozilla 1.7.8, in fact 
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20061113 Debian/1.7.8-1sarge8 displays the diacritical marks seperate, see https://bugzilla.mozilla.org/attachment.cgi?id=132874, while firefox 1.5.0.7 (Mozilla/5.0, X11; U; Linux i686; en-US; rv:1.8.0.7, Gecko/20060830) does it correctly.

Comment 20

10 years ago
The text is rendered correctly in both firefox-2.0.0.6 with pango enabled under linux, and firefox-3.0a8pre.en-US with default settings under linux too.
WORKSFORME on all platforms (except for the incorrect placement of the combining diacritical marks on Mac, which is bug 386573)
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME

Updated

10 years ago
Duplicate of this bug: 397603

Comment 23

10 years ago
i use firefox 2.0.0.7 under winxp & under win9x, the diacritical marks is still separated. but when i use windows arabic enabled, it render fine. i wait since firefox 1 until the 2.0.0.7 version, it still like that. then i try to find other ways to rendering arabic text. you can visit url: http://www.matamaya.com/encoder.htm i try to manipulate the render using javascript encoder. it works!!! but only the first line! the next lines all diacritical marks are gone! see my other bug: Bug 397325

Updated

9 years ago
Component: Layout: BiDi Hebrew & Arabic → Layout: Text
QA Contact: zach → layout.fonts-and-text
You need to log in before you can comment on or make changes to this bug.