On Fri, Feb 01, 2002 at 04:01:33PM +0600, Dmitry Yu. Bolkhovityanov wrote: > On Fri, 1 Feb 2002, Olivier Chapuis wrote: > > > So nl_langinfo and iconv should not be used :o) but it does not > > seem that there are obvious (portable) replacement (XFree >=4.0.2 > > has some Xutf8 functions, we may try to use if available). > > Please, please, please don't use Xutf8*() functions -- they are > absolutely unportable. They were introduced due to the inadequacy (sp?) > of the current X locale model: only one locale at one moment, so Xutf8*() > are "current-locale"-independent. But their unportability completely > outweighs their advantage. >
Do there are bad or only unprotable? If there are bad only because there are not protable this may be fixed as xterm do: xterm has a file with these functions in the case the "locale" Xlib does not have it (xterm -u8 work fine with XFree-3.3.6 and old glibc). What happen is that for ewmh support fvwm should deal with utf8 strings for window names: a window can gives its names with an UTF-8 string and fvwm should set on the window the names that it really used in UTF-8 (this name may be different form the original window name: xterm, xterm (1), xterm (2) ...). Moreover, more and more utf-8 strings will appear in the future. So now what we should do for performing conversion? In the average (lib)iconv seems to give good result but it speaks an other language than X. Maybe the Xutf8* function may help at some points? Any other ideas? Also what to do for displaying directly utf8 strings (with a libc which does not support utf8 locales)? Is XRender/Xft can do that? Really any suggestion is welcome. But, any way at the present time the most important thing is to centralize all the fvwm text rendering and locale stuff in 2 or 3 libs file so that we can really works on all this locale stuff which is a real (interesting) mess IMHO. 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]
