Seems like this latest addition with locale support also introduced problems for us using non-US keyboard. I get this error message every time I open a iTerm window, and the keys like ö ä å doesn't work, which is kind of annoying.
Last login: Wed Sep 10 00:54:07 on ttys000
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LC_MONETARY = "en_SE.US-ASCII",
LC_NUMERIC = "en_SE.US-ASCII",
LC_MESSAGES = "en_SE.US-ASCII",
LC_COLLATE = "en_SE.US-ASCII",
LC_CTYPE = "en_SE.US-ASCII",
LC_TIME = "en_SE.US-ASCII",
LANG = "en_SE.US-ASCII"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
iTerm
Terminal emulator: VT100/ANSI/XTERM.
Version: 0.10
"Now automatically set up locales when launching a shell"
Feedback Type: Usage Tip
Contributed by: frpet1 Wednesday, September 10 2008 @ 11:51 AM PDT
Product Platform: MacOSX
Used Product For: Over One Year
Comments
"Now automatically set up locales when launching a shell" - OttoCom
Same with fr_FRperl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LC_MONETARY = "en_FR.UTF-8",
LC_NUMERIC = "en_FR.UTF-8",
LC_MESSAGES = "en_FR.UTF-8",
LC_COLLATE = "en_FR.UTF-8",
LC_CTYPE = "en_FR.UTF-8",
LC_TIME = "en_FR.UTF-8",
LANG = "en_FR.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Friday, September 12 2008 @ 04:32 AM PDT
"Now automatically set up locales when launching a shell" - luukman
same problem here...perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LC_MONETARY = "nl_NL.US-ASCII",
LC_NUMERIC = "nl_NL.US-ASCII",
LC_MESSAGES = "nl_NL.US-ASCII",
LC_COLLATE = "nl_NL.US-ASCII",
LC_CTYPE = "nl_NL.US-ASCII",
LC_TIME = "nl_NL.US-ASCII",
LANG = "nl_NL.US-ASCII"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
fortunately I haven't found any keys that are not working.. But I would like to know how to fix this.
Regards
Reply to This
Thursday, September 11 2008 @ 10:48 AM PDT