This was exactly my reasoning, and now I cannot understand what I have
changed in order to make it work.
now, the debugger is launching with my user name at the command prompt
and all of my personal environment, etc. settings re invoked.
As I am the Login user of the app, the environment, etc. is being read.
I have now tried several times and never get the LANG warning message.
I added
setenv LANG "C"
to login.mine
then invoking env
LANG=C
As explained in the perl README this is just bypassing the primary
issue of:
why, in particular, :
LANG = en_US is not valid and causes the warning message.
there is no entry for en_US or any of the other possible variations.
in the usr/share/locale directory.
anybody using any of the others?
cs/ el/ es/ fi/ hr/ it/ ko/ no/ pt/ ru/ sv/
de/ eo/ et/ fr/ id/ ja/ nl/ pl/ pt_BR/ sl/
I assume the warning is generic to the Perl application as you will see
it
even when you perl -v on the command line.
Also, by default, LC_ALL is undefined. Any opinions about this setting.
finally, I have scripts which process Japanese text or english depending
on the value of the bytecode.
I will have to go back and look at the code as I don't recall any heavy
utilization of or reliance on locale.
In older Mac OS I would always make my system happier by switching the
primary script to Japanese. Though I mostly use English. Then some of
the apple updates would fail because of the incorrect script. This
meant temporarily changing back for the upgrade process. So, with that
experience behind me, I doubt we want to really Change the system
script, just the environment script where perl is running.
At this point, it looks like using "C" for English and other scripts are
available.
however,
en
en_US
en_UK
en_ (I forget)
are all missing, yet supported in the system by default?
Jim Cooper
On Thursday, May 10, 2001, at 07:58 AM, Wilfredo Sanchez wrote:
>
> On Monday, May 7, 2001, at 05:49 AM, Jim Correia wrote:
>
>>> possibly, the settings which are in my Login.mine Environment.mine ,
>>> ...etc. files had not propagated when I originally tried the
>>> functions from within BBEdit.
>>
>> I'm not sure if those files are "run" when you start a GUI app. They
>> are run when you start a new shell session. If anyone knows how to
>> set environment variables for GUI apps please pass along the
>> information.
>
> loginwindow launches Finder launches BBEdit. Your shell hasn't had a
> chance to do anything in that path. This differs from X11, where I
> think your shell is invoked to launch your X session.
>
> -Fred
>
---------------------------------------------------------------------------
reply directly to:
mailto:[EMAIL PROTECTED]
iMedia, Ltd.
Tokyo
---------------------------------------------------------------------------
