On 9/22/07, Jussi Peltola <[EMAIL PROTECTED]> wrote:
> Filenames in foreign languages can sometimes be a little problematic,
> because Unix doesn't really have any standard on how to store them on
> disk - filenames are just byte arrays. Because a machine may have users
> with different locales this can make sharing files very difficult, so
> the desktop environments seem to be storing filenames in UTF-8 with no
> regard to the locale.
> GTK apps also look at the environment variable G_FILENAME_ENCODING,
> which you may want to define, but if memory serves me correctly it
> defaults to UTF-8 so with an UTF-8 locale you don't need to care.
>
> Are you sure .profile is sourced in your X session? Try checking the
> environment variables are set in an xterm.
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
> remember if OpenBSD has one (I'm stuck on a painful mobile device so I
> can't check).
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,
> Jussi Peltola
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFG9UGo0SX92aZxWNIRAuVUAKCEoA+wg57S7VA9saaiJ/3vjGcyOQCdEZnb
> JtD1KDPlmqEO51PrrcMOYiw=
> =b0l1
> -----END PGP SIGNATURE-----
