On 29 Apr 2002 11:31:28 +0200, Olivier Chapuis wrote: > > And the last thing is that every things seems to work. The test > I done: > > MenuStyle * Font -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1 > # replace /opt/kde to KDE3 dir > ImagePath > +:/opt/kde/share/icons/hicolor/16x16/:/opt/kde/share/icons/locolor/16x16/ > DestroyMenu kde-sys > AddToMenu kde-sys DynamicPopupAction PipeRead 'fvwm-menu-desktop --desktop > kde-sys --lang ar --enable-mini-icons --mini-icons-path apps' > > Then, "Menu kde-sys" gives me an Arabic KDE3 menu which seems > good (however, Arabic characters are separated and not ligatured, > is this fvwm fault?).
I did the same test with KDE 2.2 with your yesterday's commit (it does not work without it) using C locale. It seems that KDE 2.2 was not translated to Arabic, so no results here. Russian - fully works, French - minor problems, Hebrew - minor problems. All problems are KDE-specific, not FVWM. For example, they use 'é' (which is not how it should be written in utf8) in all Programmes submenus, so entries look like "Syst*", Multim*ia" etc, other submenus are good. And they use visual Hebrew, so together with Bidi it becomes logical (i.e. reversed). I hope that KDE 3.0 has logical Hebrew and Arabic. > i.e., if the font name does not use a standard charset/encoding > the encoding can be added after the font name and after a "/" > separator. Other info can be given: > > font_name/encoding[/iconv_name[/mb_info]] > > where encoding is a standard encoding (supported by fvwm) and > iconv_name is the encoding for the system iconv implementation > (there are no standard here). Maybe some multibyte font info > maybe needed in a near future (specially for Xft font). > The advantage of this method is that we do not need to add new > config command (for fvwm and all the modules that load font), > we keep the idea that font define the encoding and that in most > situation nothing special should be added to a config file. > I propose the / for separation as ",", ";" and ":" are already > used in font name but any suggestion is welcome. I think it is good. This is needed anyway for unicode that has more than one encoding, i.e. utf16 and so on. And I think we should support also specifying an encoding with the string itself (this overrides the default encoding used from fonts). I suppose this should work already when XbmString* functions are used; an encoding may be specified using escape sequences (would be nice to have any spec about this). Nice work, Olivier. We have a nice internationalization. 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]
