On 24 Apr 2002 18:15:49 +0000, Mikhael Goikhman wrote: > > On 24 Apr 2002 06:56:05 +0200, Olivier Chapuis wrote: > > > > On Fri, Apr 19, 2002 at 01:21:55AM +0000, Mikhael Goikhman wrote: > > > > > > 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? > > Hmm, not yet. > > My glibc-2.2.90 does not support utf8 locales (I don't know how .90 is > possible if the latest is 2.2.5). > > I upgraded to glibc-2.2.5. This broke all my programs that use atexit(), > I don't know why they did it. Anyway, glibc-2.2.5 supports utf8 locales. > > XFree86-4.1.0 does not seem to support utf8 locales, at least I added > as you suggested these lines to locale.alias, it does not work. > > ar_JO.utf8 ar_JO.UTF-8 > en_US.utf8 en_US.UTF-8 > he_IL.utf8 he_IL.UTF-8 > ru_RU.utf8 ru_RU.UTF-8 > > So I upgraded X to XFree86-4.2.0. The same result. > Xlib does not support locale en_US.utf8. Ideas?
Ok, changes to locale.alias do not work, but if I use the locales from the right column, both glibc and Xlib support them. I am now experimenting, the main problem is that I don't have true unicode fonts, specifying "*-iso10646-1" gives some subset. I also get this behaviour. When running with LC_CTYPE=en_US.UTF-8 and I specify incorrect font, it may wait several seconds. Error messages are not polished. I will try to improve them a bit later. *-iso8859-1 font gives this: "*T*i*t*l*e" where "*" is empty square, while *-iso8859-N (where N is from 2 to 15) shows it right: "Title". Why is it? > > - 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) When I use: Style * Font "xft:Luxi Mono:Medium:Roman:size=14:encoding=iso10646-1" only latin is displayed, but I can see where are spaces and see that Bidi is applied to Arabic/Hebrew in utf8. I use this app for testing (where ar_JO may be replaced by he_IL, ru_RU): xmessage -name "`env LANG=ar_JO.UTF-8 date '+%a %d/%b/%Y'`" nothing When I use (fvwm is still run under LC_CTYPE=en_US.UTF-8): Style * Font *something_from_426_unicode_fonts*-iso10646-1 it works as expected except that I don't have unicode fonts for Arabic (*-arabeyes-1 seems unusable at all, and another my *-iso10646-1 has only Arabic, not latin). I am able to see Russian and Hebrew without problems. Bidi works well with utf8. Regards, Mikhael. -- 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]
