Following up on shell(locale) problem
pete at mollysrevenge.com
Tue Mar 1 19:24:17 EST 2011
Thanks Mike. 'Fraid the command you gave me still returns the incorrect info when executed with the LC shell command.
In answer to your other email, I'm trying to get this info so I can format numbers and currency in my application according to the user's preferences, rather than having the user specify the same preferences to my application. But it's quickly becoming more trouble than it's worth!
-------------- next part --------------
On Mar 1, 2011, at 4:04 PM, Mike Bonner wrote:
> Ok, while this doesn't solve the issue, if you do
> shell("LANG=en_US.UTF-8;locale -k LC_NUMERIC")
> You get back the correct info yes?
> The problem here is that (I think someone said this farther up) the process
> shell uses isn't the same as a full blown terminal start. If you have a
> .bash_profile file in your user directory, and you do
> shell("source ~/.bash_profile ; locale -k LC_MONETARY") does it work?
> On Tue, Mar 1, 2011 at 4:48 PM, Peter Haworth <pete at mollysrevenge.com>wrote:
>> OK, In terminal, that returns "LANG=en_US.UTF-8". With the LC shell
>> command, it returns nothing!! There's definitely something weird going on
>> with the LC shell command.
>> Pete Haworth
>> On Mar 1, 2011, at 2:44 PM, Mike Bonner wrote:
>>> I'd still be curious to know if
>>> env; |grep LANG
>>> returns the same environment variable value both from LC shell, and from
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode