I just want to provide GRASS64 in two languages and without the user has to define lang in the bash_profiles.<div>My idea was to create 2 files: grass64eng and grass64sp each one with different language sets. So the user would have only to select the adequate file. If this is not correct, what would be your suggestion?</div>
<div><br>Thank you in Advance</div><div>Gilbert<br><br><div class="gmail_quote">On Tue, Feb 2, 2010 at 7:07 PM, Glynn Clements <span dir="ltr"><<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
Gilbert Ferrara wrote:<br>
<br>
> For instance If I want to have 2 language sets available for a user, can<br>
> have two different bash_profiles? I mean have grass64eng for english<br>
> language and grass64sp for Spanish?<br>
> And are there any rules regarding bash_profiles files?<br>
<br>
</div>~/.bash_profile is read when starting a login shell. It isn't started<br>
for non-login shells.<br>
<br>
If you want to provide separate versions of the grass64 script, bash's<br>
startup files aren't relevant.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">Glynn Clements <<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>><br>
</div></div></blockquote></div><br></div>