On Fri, Feb 01, 2002 at 11:16:18AM -0500, Dan Espen wrote: > Olivier Chapuis <[EMAIL PROTECTED]> writes: > > On Thu, Jan 31, 2002 at 09:41:39PM -0500, Dan Espen wrote: > > > > > > I have multibyte enabled. > > > With the latest CVS I get this warning: > > > > > > [FVWM][FInitCharset]: WARN -- Cannot get charset with CHARSET env variable > > > > > > Where do I find the documentation on this env variable? > > > > > > > Hum, I do not know if there is a documentation somewhere. This variable > > is used by some programs in the gnu world to get the charset associated > > to your locale if your libc does not have nl_langinfo which can do the > > job (it seems that you do not have nl_langinfo). It can also be used to > > override the charset returned by nl_langinfo. > > Now, it is not used in mb support but in the ewmh support for iconv > > conversion from/to UTF-8 and your charset. If you have iconv > > you can get the list of charsets by using "iconv --list". > > There are multiple problems here: > > > > 1 - FInitCharset is run by fvwm even if you do not have iconv > > support (easy to fix). > > 2 - nl_langinfo may return a different charset than the "X charset". > > 3 - iconv is not an X function. > > > > 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). > > I will try to fix these problems progressively. I begin to understand > > the X i18n stuff. Any way these problems are small and these concern > > only applications with ewmh support (but these should be fixed). > > I looked at the various codesets iconv supports to try to figure out > a default value. > > It looks like if CHARSET is not set, is should default to ISO_8859-1 > (on Linux). > > On Solaris and AIX, the default should be ISO8859-1. > > On HPUX, it looks like it should be either "amere", "iso81", or "engle". >
How to set this default? Do we have "cpp variables" which allows to write down somthing like: #ifdef SYS_A #define DEFAULT_CHARSET "FOO" #endif #ifdef SYS_B #define DEFAULT_CHARSET "XYZ" #endif ...etc in libs/defaults.h ? > I'd be happy if it just didn't print any warning. > Why are you against such warning? This may help to debug the (experimental) iconv stuff. For example, with the error message you send to me I can see that you do not have nl_langinfo and that no iconv conversion will be performed at all. On the other hands, we can document our use of the CHARSET variable. But as our UTF-8 support is not finalized this should wait a bit. Any way, if you really want I can suppress such warnings now or only in the future beta version of 2.5.x. 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]
