Apache OpenOffice (AOO) Bugzilla – Issue 97921
Cannot get proper rendering of Arabic script with Scherezade font
Last modified: 2013-01-29 21:39:27 UTC
I've enabled CTL. I've got Arabic text. 1) The text left-justifies in the cell even when the sheet and the cell are both RTL. 2) the big problem. The letters are rendered without the proper joining.
Created attachment 59285 [details] File that shows the problem
Created attachment 59286 [details] Image of the problem
Confirming, not related to Calc, same in Writer. Using the Mac OSX provided Geeza Pro font shows no problem. But I guess it is not OOo-Related. TextEdit has the same problem, and Mac OSX font-preview displays dotted marks for Scheherazade, but not for Geeza Pro. So would be nice if OOo would support the font as it does on Linux, but not sure whether much can be done. Reassigning to mac porting project.
Created attachment 61289 [details] Mac OSX itself has problems with the font...
addendum: I just noticed that there is a special ATSUI variant available that doesn't exhibit the problem (only available as Freeware release, not under OFL) http://scripts.sil.org/arabicfonts http://scripts.sil.org/ArabicFonts_Download Unfortunately the AAT (Apple Advanced Typography) font is named "Scheherezade-AAT", so it is not automatically used when opening a document that uses the Scheherezade font. One needs to add a font-replacement or change the font manually. So the question is: is an ICU based renderer available on the Mac (maybe as fallback/option)? If not, will one be added?
*** Issue 84473 has been marked as a duplicate of this issue. ***
We'll use CoreText on newer versions of OSX. ATSUI just doesn't handle the required OpenType features that the normal version of Scheherezade demands. ATSUI also has other problems in BiDi scripts such as issue 98790.
*** Issue 103766 has been marked as a duplicate of this issue. ***
the problem appears in OOO310m19 also !! NeoOffice project had this problem before and they released a patch for it. the problem existed in version 2.2.5 of NeoOffice and it has been fixed with patch 7. maybe we can look at their patch and we may know what exactly the problem is ..
NeoOffice doesn't contribute back any code. And we cannot simply take it, because they chose to use an incompatible license. So people don't bother having a look at neooffice because otherwise NeoOffice folks claim we stole their code, even when only the basic idea is taken and the code written from scratch (has happened in the past already).