Oh. And since it's UTF-8, and it looks correct in the file apparently (which
is weird with no LANG env variable) would that affect how you have to manage
the results? I'm definately not a font guy, so dunno the answer to that.
On Tue, Mar 1, 2011 at 5:04 PM, Mike Bonner <bonnm...@gmail.com> 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 <p...@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
>> > terminal
>>
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
