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

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=6626





------- Comment #14 from behnam at irmug.org  2006-03-09 13:18 PDT -------
(In reply to comment #13)
As far as I know, currently Camino and Firefox do the contextualization based
on Unicode point of individual shaping of each letter. It's much better
solution than the current situation but bear in mind that it doesn't support
fine typographic features of the font (if present) and also the fact that this
solution will be limited to the fonts which do encode the Unicode points for
glyphs for Arabic Presentation forms A and B of Unicode. It will solve %99 of
current problem but it shouldn't be considered as definite solution to Arabic
rendering because many fine fonts do not encode presentation forms with Unicode
points and rely only on OT features to produce them.
Some other languages of Arabic script like Kurdish have some letters that do
not have any Unicode point for their presentation forms at all. They uniquely
rely on font technology to provide them.
The definite solution would be to fully and completely support OT, directly or
via translating to AAT.


-- 
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.