Thank you Glynn.<div>For instance If I want to have 2 language sets available for a user, can have two different bash_profiles? I mean have grass64eng for english language and grass64sp for Spanish?</div><div>And are there any rules regarding bash_profiles files? </div>
<div><br></div><div>Thanks</div><div>Gilbert<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5"><br>
<br>
</div></div>These would normally be set in e.g. ~/.profile (or ~/.bash_profile<br>
etc; there are quite a lot of files which may be read by the shell)<br>
then inherited by all processes.<br>
<br>
Setting environment variables in Unix is done with e.g.:<br>
<br>
LANG=es_ES<br>
export LANG<br>
<br>
I'd advise against using LC_ALL, as it overrides LC_NUMERIC. This can<br>
cause numbers to use a comma as the decimal separator, which is<br>
problematic when writing files (most file formats require a period).<br>
<br>
GRASS modules only use the LC_MESSAGES category directly, but some<br>
programs and (especially) scripts invoke external programs which may<br>
be affected by the LC_NUMERIC or LC_ALL settings (scripts which use<br>
awk are prone to this, although I think that we have now found them<br>
all and forced LC_NUMERIC=C).<br>
<font color="#888888"><br>
--<br>
Glynn Clements <<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>><br>
</font></blockquote></div><br></div>