211921 - CTL (complex text layout) does not render sun-devanagari properly

Status: RESOLVED WONTFIX

(Core :: Layout: Text and Fonts, defect)

Description

[kapil]

User-Agent:       Mozilla/5.0 (X11; U; HP-UX 9000/785; en-US; rv:1.5a) Gecko/20030703
Build Identifier: Mozilla/5.0 (X11; U; HP-UX 9000/785; en-US; rv:1.5a) Gecko/20030703

Here are some fixes to the handling of anuswara and chandrabindu in
the devanagari ctl mozilla shaper. The cvs diff is here:

http://www.arbornet.org/~marcow/diff

Please commit this fix to the mozilla cvs.

Also, there is a problem with the sun Saraswati fonts, the double-ka
glyph 0xf845 is missing. I checked using:

$ xfd -start $(printf "%d" 0xf845) -fn
'-cdac-saraswati-medium-r-normal-devanagari-25-240-75-75-p-240-sun.unicode.india-0'

Can you please arrange for the font to be fixed.


Reproducible: Always

Steps to Reproduce:
1. configure mozilla with --enable-ctl
2. run the mozilla and go to the test URL
3. the devanagari rendering of anuswara and chandrabindu is wrong

Actual Results:  
wrong devanagari rendering, can be detected by any native hindi reader.

Expected Results:  
should render the anuswara and chandrabindu properly

Comment 1

[Boris Zbarsky [:bzbarsky]]

.

Comment 2

[Alok Kumar]

More precisely, bug 212583 (for a character containing chandrabindu) and bug
212770 (for a character containing bindu) are subsets of this bug.

Comment 3

[Alok Kumar]

*** Bug 212770 has been marked as a duplicate of this bug. ***

Comment 4

[Alok Kumar]

*** Bug 212583 has been marked as a duplicate of this bug. ***

Comment 5

[Jungshik Shin]

Prabhat, this problem has been known to you (as we talked the other day). Let's
fix this along with other CTL-related bugs for which we've had patches for a while.

Comment 6

[kapil]

Attachment: patch to fix this (cvs diff)

Comment 7

[kapil]

Attachment: testcase

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Simon Montagu :smontagu]

Do we still need this on trunk or any current branch? The test case seems to render OK in a build with --enable-pango.