[ale] bash script error

James P. Kinney III jkinney at localnetsolutions.com
Mon Mar 19 19:04:38 EDT 2007


On Mon, 2007-03-19 at 13:27 -0400, Paul Cartwright wrote:
> On Monday 19 March 2007 10:39:58 am James P. Kinney III wrote:
> > > ok, so I just checked LANG and:
> > > # echo $LANG
> > > en_US.UTF-8
> > >
> > >
> > > is that bad???
> >
> > For _most_ things it's OK. But _some_ bash stuff and _some_ perl stuff
> > it will cause read errors with the files. There are a lot of perl
> > modules that don't support internationalization.
> 
> ok, so what is BETTER for.. most things, and how do I change it?

If your set LANG=C, it will work 99% of the time. It is a subset of the
en_US.UTF-8 character format. But the "C" designation is a bazillion
years old and is destined to go away eventually.

What I do is simply watch for weird compile errors or file read errors
and just the the variable manually as needed to "C".

You can do this from bash with "export LANG=C". If you want to make it
permanent, add that line to your ~/.bashrc file. 
> 
-- 
James P. Kinney III          
CEO & Director of Engineering 
Local Net Solutions,LLC        
770-493-8244                    
http://www.localnetsolutions.com

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part




More information about the Ale mailing list