On Wed, Apr 24, 2002 at 12:41:38PM -0700, Nadim Shaikli wrote: > On Wed, 24 Apr 2002 06:56:05 +0200, > "Olivier Chapuis" <olivier chapuis free fr> wrote: > > > > 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? > > I'm not sure what you mean by "loading the 10646 font", but you can > download the non-truncated 10x20 font using the link(s) below, > > http://www.arabeyes.org/download/external/vim/10x20.bdf.gz > -or- > http://www.arabeyes.org/download/external/vim/10x21.pcf.Z > > Note: the internal names of the fonts within the files might differ, > please check 'mkfontdir' output (fonts.dir) for appropriate > names -- if you have problems, don't hesitate to let me know. >
The problem here is that the end of an X font name should/must be the charset. So I was/am surprised by "full10x20-1". So it seems that full10x20 denote a font size ??? If this is the case I suggest that you send a bug report to http://www.arabeyes.org/ :o) > > > > 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) > > Well, I'm not sure why all that is needed (I'm simply trying to display > a few glyphs not alter my keyboard mapping, or specify date/currency > settings, etc). By the way, I'm able to use multiple Arabic-enabled > utilities without having to touch any of what is noted above (locales, > libc support, etc) given the availability of the fonts and a rendering > engine (glyph displayer) and Bidi (fribidi) - one such application is > vim-6.0/6.1. > Yes and you use a special font made for vim ... Maybe you start vim with some options? Moreover, I think that vim use an other method than fvwm to display strings. Also some applications (KDE2&3/GNOME2) use only utf8, but this is not possible with fvwm (we cannot ask everybody to use only utf8 in configuration files). Moreover, most of these applications use (lib)iconv which can cause portability problem (basically we should also ask everybody with a non (or old) GNU system to install gnu libiconv). Here the problems: 1 - if we want to make some bidi conversion on a string we _must_ know the encoding used by the string. The only good general method I found is to look at the font name of the used font and to extract the charset/encoding from this name. There is a precise specification here from the X Consortium, the last two "items" of a font name should be the CHARSET_REGISTRY and the CHARSET_ENCODING. Then, if you use a font which does not respect this standard no conversion will be done. If you use a font which use a strange charset name as say "my_arabic-36" we may "fix" fvwm so that fvwm understand this name in one second (if it correspond to an encoding that fribidi support). This may become configurable in a special way in the future. A simple alternative would be to add a new fvwm Style (and new module config options) to specify the charset of the font ... (basically xterm use this method with the -u8 option), but I do not like so much this idea. I prefer that the font define the encoding used by the user. 2 - After fvwm have determined the charset and load the font it should display the string (forget bidi here). With an unibyte font (as iso8859-X) there are no problems. Why do you not use iso8859-6 fonts with fvwm? Do you need others characters than ASCII and Arabic one's? With a multibyte font (as iso10646) locale is important, as fvwm use a (powerful) method from X to display string and load font. Good fonts are automatically loaded (no need to specify the charset) and string are well displayed without the need to think to much :o) So with iso10646, at the present time, you should use an utf8 locale (or good ttf font and XFree-4.good_version, here yet an other method is used). Now as utf8 grow in importance and a lot of system does not support utf8 locale I will see if fvwm can support utf8 on system which does not support utf8 locale. You may be happy with this but you should wait a bit. Ooops, this works now on my machine but I cannot commit the change before Monday, this should work on any X server (I have added a 4th method to display string ...). > On the same related-topic what about those that are not running linux > per se, but are using various unix flavors (at work, for instance, I'm > on a Sparc Solaris (SunOS-5.7)). > Fvwm is not written for Linux. We try to do so that fvwm can work on any system that can run an X server. I hope that fvwm has no problem with Sparc Solaris. However, some fvwm developers use Linux, GNU tools/libs and XFree so it may happen that there are some problems with "exotic" architecture (specially if there are not gnushed or/and XFreed), but we always try to fix these problems. Regards, 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]
