On 9/22/07, Jussi Peltola wrote:
I don't know what you mean by sourced, but when I type "set" xterm I see them.
> The command locale will also print out the locale settings, but I can't
I don't think it has one either. In any case I noticed that indeed
the two "sets" weren't really accepted by the system:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LC_CTYPE = "he_IL.UTF-8",
LC_COLLATE = "he_IL.UTF-8",
LANG = (unset)
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Can't resolve locale
> Do the filenames look ok if you ls them in an xterm?
OK, I checked that and they don't. They appear like gibberish and
question marks surrounded by circles. I guess this conforms to the
above perl warning. Maybe there just isn't a "he_IL.UTF-8" locale for
OpenBSD.
> HTH,
| Justin C. Sherrill | Re: pkgsrc bulk build and tiff |
| Linus Torvalds | Linux 2.6.27-rc5 |
| Ingo Molnar | [crash, bisected] Kernel BUG at ffffffff8079afb1 (__netif_schedule()) |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Evgeniy Polyakov | Re: tbench wrt. loopback TSO |
