[Webkit-unassigned] [Bug 6626] Arabic & Farsi rendered with no shaping (all glyphs separate, unreadable!)

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Sat Feb 11 20:56:11 PST 2006


------- Comment #11 from behnam at irmug.org  2006-02-11 20:56 PDT -------
(In reply to comment #10)
> I think the real solution is to make the OS X text system properly understand
> the information in these fonts for shaping Arabic and Farsi scripts. This would
> best be done by filing an appropriate Radar bug against the OS X text system.

This issue is not unknown to Apple. Based on indications that I get from Apple
(which is none!) and based on few things that I know about the complexity of
this task, I think that interpreting Uniscribe contextualization in AAT
environment is not for anytime soon. Even if the next OS (and not the next
update) implements this interpretation, it will be full of bugs for quite some
time and we will regret not having that icon on menu bar!
This solution is a practical solution based on the reality. And I also fully
disagree about being inelegant. It's just a button that helps us out until
Uniscribe is fully interpreted... bug free.

Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list