Email List: Xaustin-group-lX
[All Lists]

Re: Invalid shell assignments in environment

To: chet.ramey@xxxxxxxx
Subject: Re: Invalid shell assignments in environment
From: wollman+austin-group@xxxxxxxxxxx
Date: Thu, 2 Jul 2009 17:01:05 -0400
Cc: austin-group-l@xxxxxxxxxxxxx
References: <200907012242.n61MgCCp020103@penguin.research.att.com><4A4C2005.6030402@case.edu><4a4c81a6.2tWl4Z9DpJUyvd+z%Joerg.Schilling@fokus.fraunhofer.de><200907021327.n62DRe5k029384@penguin.research.att.com><20090702143325.GA5491@squonk.masqnet><4A4CCA35.6070009@cateee.net><4A4CCBE1.7020801@case.edu><20090702150847.GA6190@squonk.masqnet><090702183047.AA87319.SM@caleb.INS.CWRU.Edu><4858.76.191.129.144.1246561262.squirrel@webmail.sonic.net><20090702202320.58C5B2B208F@mx5.roble.com><090702205546.AA88203.SM@caleb.INS.CWRU.Edu>
<<On Thu, 2 Jul 2009 16:55:46 -0400, Chet Ramey <chet.ramey@case.edu> said:

>> One question though, are we talking about a portable character set for
>> variable names, variable values, or both?   Don't know if there's a need to
>> ensure the portability of values but I see a substantial value in
>> standardizing the character set for variable names, to ASCII ideally.

> Variable names.

Hmmm.  In what character set is the value of the LANG and LC_*
environment variables?

-GAWollman

<Prev in Thread] Current Thread [Next in Thread>