I have set LANGUAGE to the locale that enlightenment will be trying to
use. This is done deliberately to be able to identify the langauge of
e17 through at least one environment variable.
I Assumed that most programs use LC_ALL or LC_MESSAGES to identify which
locale to use or which messages file to use for translations. I assume
we can add an environment variable called E_LANG for this purpose.
Can you explain why you do not want e to set any environment variables?
If we do the following
$ export LC_MESSAGES=en_US
$ export LANGUAGE=NULL
$ enlightenment_remote -set-lang ""
after E starts it will have LANGUAGE=en_US in its environment. Why would
this not be wanted?
-shorne
On Sat, 2005-12-03 at 15:33 +0530, Ramkumar R wrote:
> > Sorry, I made a few changes.
>
> You still seem to be setting LANGUAGE to (LC_MESSAGES || LANGUAGE ||
> LC_ALL || LANG), when one of them is non-null... Consider for example,
> LC_MESSAGES = en_US, and LANGUAGE = NULL. That's why I moved that code
> to the `else' part and set _e_intl_language later.
>
> Ramkumar
>
> --
> WARN_(accel)("msg null; should hang here to be win compatible\n");
> -- WINE source code
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
