Apache OpenOffice (AOO) Bugzilla – Issue 49650
the characters whose glyphs are missing in the default font are not displayed at all.
Last modified: 2005-12-11 18:58:18 UTC
OOo should use a suitable font to display certain characters when the default font lacks the respective glyphs. instead, it displays blank spaces. there is a workaround to type in a document in arabic script: select all the text (which looks like a number of blank spaces) and change the font to a proper one. in this case *you* are doing the searching for OOo. but this causes problems specially when you search some text or add a hyperlink. when you type something containing special character into the search box or hyperlink box, the search criteria is not displayed. the only workaround is to change the default font that writer uses, which is not very desirable.
Please attach a sample document and name the fonts you're using. If you use a broken font that claims to have the characters there's nothing OOo can do about that.
Reassigned to US.
no response, no sample document -> invalid.
closing. reopen this issue after you provided the necessary information.
i will attached a file written in Arabic script using the font courier. as you can see, nothing is visible except some common characters.
Created attachment 27300 [details] file written in arabic script using courier font
Created attachment 27301 [details] the same file, using a different font having arabic glyphs (I'll also attach the font)
Created attachment 27302 [details] copy this file into ~/.fonts/ directry
Are you show that you append the correct file? The file "fontbug.odt" tells that it is written in "nazli". Both documents display well on my system, without installing nazli.ttf. I've got WinXP Home German and OOo1.9.104.
not reproducible on linux either (m110) - works well with the font (font is used) - works well without the font (fallback to another one) Please try with a more recent milestone, there have been problems with creating OOo's own fontcache. Maybe this is causing trouble in this case as well.
The reporter's points are all upright and valid. And such a feature is already present; we call it GlyphFallback. But a precondition to let this work is to set the document language appropriate, which isn't the case in the attached file. Hint: this also should work automatically but curently does not due to another issue. Set the script type in Tools/Options/Language Settings/Languages by marking the check box for Suport of complex scripts and select a Language. As a consequence you'll e.g. now encounter two entries in e.g. Format/Character/Font dialog: one for western text and another one for Complex scripts. Other dialogs also experience further CTL specific feature settings. If this doesn't solve this issue for you completely, we 'll probably have an issue in the GlyphFallback code for CTL-Arabic only, as the majority of the GlyphFallback works pretty well. Pls. report you findings back in here after setting the document's language to CTL/Arabic as described above. Thx.
us: sure? The language is set to "Farsi" when I open the doucment. This should be OK. But again: fallback works here.
to us: i applied those settings and it worked. but the problem is still there when you want to search a string in the text or insert a hyperlink. the search/hyperlink window text boxes do not support CTL and as you said, the GlyphFallback doesn't work. i'm using milestone 104.
@us: Please explain why Farsi as language is not OK.
@submitter: the problems in dialogs you're facing are due to an incapable UI font and a missing GlyphFallback candidate OO.o is aware of (remember the GlyphFallback list is limited for performance reasons). Make sure you've selected a scalable (TrueType or Type1) font for the GUI in gnome-font-properties that supports arabic. Watch OO.o's GUI font change on the fly when configuring gnome-font-properties. Additional workaround: install a J2re from Sun. The font family Lucida provided along with Java is suitable for arabic and is normally found by OO.o and utilized for GlyphFallback. =>still WFM.
@us: Please explain why Farsi as language is not OK. The problem is that OOo doesn't find a font with arabic glyphs when the language is set to Farsi, but succeeds when one sets the language to Arabic. Farsi uses arabic letters as well. You wrote: > But a precondition to let this work is to set the document language > appropriate, which isn't the case in the attached file. So my question still is: Why is Farsi not a suitable language in this case?
US, would you *please* answer? You wrote: > But a precondition to let this work is to set the document language > appropriate, which isn't the case in the attached file. So my question still is: Why is Farsi not a suitable language in this case?
cloph, important to let ctl, (bidi) font rendering work correctly is the setting of the default _document_ language under "Tools/Options/Language Settings/Languages" to the appropriate language (precondition: CTL checkbox has to be checked). This currently does not work automatically and leads to all kinds of problems. Refer to issue 32939 - fixed for 2.0.1. The attached documents have Farsi set as paragraph language which is not the same. (Any discrepancy between available paragraph languages and default document languages are probably a different issue.)
Well, then there is no reason to keep this issue.. Marking duplicate. *** This issue has been marked as a duplicate of 32939 ***
closing duplicate