Apache OpenOffice (AOO) Bugzilla – Issue 27689
no lam alif ligature replacement when the font don't contain arabic glyphs
Last modified: 2004-08-16 16:21:47 UTC
When i set the font to Times, then type a lam, then an alif, i get a normal lam connected to a normal alif instead of a lam alif ligature. This does not happen for the other fonts i have tried. When you type a lam then an alif, these two characters should be replaced with a lam alif ligature. I have opened OOo 1.1.0 and 1.1.1 side by side to try this out. The bug only shows up in 1.1.1.
please provide a sample document showing the behavior, please provide a screenshot as well. What (Arabic) fonts do you have installed on your system ?
Created attachment 14523 [details] document illustrating the bug, with embedded screenshots
Here are the Arabic fonts i found on my system, but maybe you have other suggestions of where to look: /usr/X11R6/lib/X11/fonts/drakfont/ttf/Naqsh.ttf /usr/share/fonts/ttf/arabic/KacstDecorative.ttf /usr/share/fonts/ttf/arabic/Kacst-Qr.ttf /usr/share/fonts/ttf/arabic/KacstArt.ttf /usr/share/fonts/ttf/arabic/KacstBook.ttf /usr/share/fonts/ttf/arabic/nastaliq_unicode.ttf /usr/share/fonts/ttf/arabic/KacstDigital.ttf /usr/share/fonts/ttf/arabic/KacstLetter.ttf /usr/share/fonts/ttf/arabic/KacstPoster.ttf /usr/share/fonts/ttf/arabic/KacstTitle.ttf /usr/share/fonts/ttf/arabic/KacstTitleL.ttf
A great sample document. Thanks! Now I see what the problem is. Since the fonts you selected do not contain support for Arabic and not even for the required glyphs, a "glyph fallback" is performed. This glyph fallback should take care of the shaping too, but it fails. Need to analyze...
Fixed in CWS vcl22. HDU->HDU: fixed merging single charpos into BiDi fallback run. Since this has been a general problem that may have occurred in a lot of circumstances the priority should be increased to 3.
*** Issue 22336 has been marked as a duplicate of this issue. ***
Thanks for fixing this so quickly.
*** Issue 23769 has been marked as a duplicate of this issue. ***
reopening for reassignment
HDU->US: please verify Tesing hint: make sure that there is no non-X11 Times font available for the display.
changing back to FIXED after reassignment
Unfortunately this does not work for me. If Lucidasans isn't available font fallback seems to find a reasonable alternative (as seen on my W2k host). But on Linux where Lucidasans is available (found in pspfontcache) the lam-alif characters are represented by the well known rectangle. Apparently a Lucida XFont is used.
Reassigning to HDU.
HDU->US: As discussed, this fix is for the problem, that glyphs get reversed when the glyph fallback is triggered in a RTL text for a X11 font. The issue with Lucda Sans and the Lam Alef ligure is a different problem (issue 30093), which will be addressed in a later CWS.
Setting back to fixed,
Accepting HDU's suggestion. Issue verified in cws vcl22.
Issue can not be verified+closed because of isssue 25565.
The problem here is that glyph fallback doesn't seem to work anymore. This worked in former releases. Even when the default CTL font is set to traditional arabic. Regression.
Transferring to HDU.
Tested version src680_m49.
I have to be more precise: GlyphFallback seems to work in general, but fails for the lam alif ligature.
Setting back to FIXED. I made a mistake.
As reported in issue 30093 the lam alif ligature only produces rectangles in conjunction with Lusidasans from the java package. This fix has been verified on mws src680_m50 with the "Traditional Arabic" and the "Kacst" font family.
If you want to verify this issue you shouldn't do this with traditional arabic or kacst fonts since they support arabic glyphs and no need for fallback. You should try it with other fonts that doesn't contain arabic glyphs. It's still available in 1.1.3 builds. also how come you marked this as closed/fixed and http://www.openoffice.org/issues/show_bug.cgi?id=30093 still new?