To: luther at dpt-info.u-strasbg.fr Cc: lablgtk at kaba.or.jp Subject: Re: [Caml-list] Re: postscript, printf module and coma separator. In-Reply-To: <20010612130358.A25491 at lambda.u-strasbg.fr> References: <20010608183321.A14580 at lambda.u-strasbg.fr> <20010611193053.B7177@clipper.ens.fr> <20010612130358.A25491@lambda.u-strasbg.fr> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010703113017D.garrigue at kurims.kyoto-u.ac.jp> Date: Tue, 03 Jul 2001 11:30:17 +0900 From: Jacques Garrigue Lines: 30 From: Sven LUTHER Subject: [Caml-list] Re: postscript, printf module and coma separator. Date: Tue, 12 Jun 2001 13:03:58 +0200 > > > Unfortunately, i have the LANG variable set to fr_FR, and as thus fprintf > > > outputs floats as : > > > > > > 3,14 > > > > > > but this is not a valid postscript coordinate. > > > > That seems strange. I have also LANG and LC_CTYPE set to fr_FR, and I do > > not have the problem. And that under Linux (GNU libc) and Solaris. There is > > the problem with LablGtk, because GMain.Main.init sets the locale (if you > > use the toplevel, you can not even enter a new non-integer float, since the > > ascii -> number fails on the `.'). So I think the bug is inside LablGtk, > > and should be corrected there (maybe an optional parameter to change the > > environment variable before gtk_set_locale). Sorry for the very slow answer. No, I don't believe that LablGTK does anything wrong: you have to call setlocale if you want to make possible any internationalization of your application, including fonts. In theory setting LC_NUMERIC to C should be enough to solve the problem, but this can be hairy. For hard cases, the last snapshot of lablgtk (2001-05-23) adds a ?nolocale option to GMain.Main.init, which you can use as a quick hack to disable the call to setlocale. Jacques