On Fri, Apr 19, 2002 at 01:21:55AM +0000, Mikhael Goikhman wrote: > On 18 Apr 2002 16:37:00 -0700, Nadim Shaikli wrote: > > > > Mikhael/Olivier, I downloaded a recent snapshot (20020416) to test > > out the Bidi code that was recently added. I compiled with fribidi; > > everything went smoothly - configure noted, > > > > With Bi-directional text support? yes > > > > yet I'm not sure how to go about displaying a window title in Arabic. > > I tried the following, > > > > Using a 10646 font (its used successful in many other applications), > > I defined the following entries in my fvwm2rc file, > > > > Style * Font -misc-fixed-medium-r-normal--20-200-75-75-c-100-full10x20-1 > >
Nadim, can you send me a pointer to a doc about the "full10x20" notation for loading iso10646 font? > > AddToMenu arabic-test > > + "Arabic" Title > > + "ar-test" Exec exec xterm -title Ù?رØØ?ا -e rsh otho & > > + "Ù?رØØ?ا" Exec exec xterm -title test -e rsh otho & > > > > In my .xinitrc prior to starting fvwm2, I 'xset fp+ my_10646_font_file', > > I then start fvwm2; I invoke that "ar-test" entry, the xterm appears, > > but the title is NOT displayed in arabic. The menu entry is not noted > > in Arabic either. Do note that the environment is set so that I can use > > other applications that require the Bidi library and the 10646 font (so > > they're very much loaded - I hope I don't need to muck with locales and > > such :-) > > I don't know how to tell fvwm that the encoding is utf8; using *-10646-1 > font is not enough. Setting $LC_CTYPE to, say, ar_JO.utf8 does not work. > I suppose Olivier knows. > It seems that there is two problems here. - Displaying string with a core *-iso10646-1 font: at the present time this should work only with fvwm compiled with MB support, an utf8 locale and a libc that support utf8 locale (also X should reconize the locale as an utf locale: see /usr/X11R6/lib/X11/locale/loacle.alias). Unfortunately, I cannot test this as my libc does not support utf8 locale. Mikhael, can you confirm that this work? - To apply bidi fvwm should reconize a core *-10646-1 font, I think that fvwm fail to do this because I think that the default charset with the utf8 XFree-4 locale is iso8859-1. This may be fixed after a confirmation that the first point work. I will see if we can implement the use of core *-iso10646-1 font without all the above requirement (but with XFree-4). On the other hands, I think that with a true type iso10646-1 font there is no problem (needs XFree-4.x, x>=1 and iso10646-1 ttf with arabic/hebrew/persian characters to see bidi in work) > I only tested 8-bit encodings, iso8859-6 and iso8859-8. > > Do the following. Install iso8859-6.8x fonts from: > > http://www.langbox.com/bidimozilla/fontXFE/ > > Do the same with iso8859-6 fonts in old/ subdirectory. > Run xmessage from a script (if 8-bit chars can't be typed in your shell): > > xmessage -name "a) ÓáÑ - Åâäêåê, Î×è× ÌèêÉ" "this message is not really > important, just long enough" > > I don't know what the string means, I copied it from some web site. > Do the following: > > Style Xmessage Font *-iso8859-6 # Bidi applied, visual Arabic > Style Xmessage Font *-iso8859-6.8x # Bidi not applied, logical Arabic > > The same with Hebrew: > > xmessage -name "a) îùôè áòáøéú" "this message is not really important" > Style Xmessage Font *-iso8859-8 # Bidi applied, visual Hebrew > > I tried to add now iso8859-6.8x as bidi-enabled in libs/FlocaleCharset.h, > but it failed. I tried all cases including "iso8859-6.8x" (what fonts.dir > says), "iso8859-6.8X" (what pcf says), "iso-8859-6.8X" (what url says), > nothing works. Olivier, what should be done? > Hum ..., do you try to add the line CT_ENTRY("ISO8859-6.8X", iso8859_6, "ISO8859-6") at the end of the FlocaleCharsetTable[] initialization (around line 338 of libs/FlocaleCharset.h)? What is the difference between ISO8859-6 and ISO8859-6.8X ? Olivier -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
