Dear subscribers/moderators,
Does OpenBSD fully support Hebrew? If indeed it does, how does one make
applications in X/KDE properly see/present Hebrew letters and filenames?I have already added the following two lines to my .profile:
export LC_CTYPE=he_IL.UTF-8
export LC_COLLATE=he_IL.UTF-8and this made it possible to show Hebrew filenames under normal KDE
applications properly. However, when I tried opening an OpenOffice
files, for example, which had Hebrew letters in it, it all appeared
meshed and garbled or just blanks instead of letters.Amit.
We do not have full i18n support. The locale stuff in the base system
is not finished (I know, I'm late...)Qt has its own locale system, so hebrew should work just fine in all
Qt and KDE applications (including right-to-left text).Gnome and gtk also have some support.
Vim supports more or less every script including hebrew.
I don't know if there's any issue with input, I'm not familiar with
hebrew, and I've only been working with japanese input.There might be some tweak to help OpenOffice. Does OpenOffice support
hebrew on some platforms ? If it does, it might make sense to try to
figure out the configuration differences.
Marc,
Hebrew works fine on openoffice with all the major linux
distributions. If you could suggest how to tackle this, I'd be happy
to have a look.Amit
Hi Amit,
Maybe I missed something, but you do have a Hebrew font installed on
your system and in your font path right?
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.
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).Do the filenames look ok if you ls them in an xterm?
HTH,
Jussi Peltola[demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
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").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
| Hiten Pandya | Re: up? (emacs docbook xml ide) |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Linus Torvalds | Re: LSM conversion to static interface |
| Ingo Molnar | Re: AIM7 40% regression with 2.6.26-rc1 |
git: | |
| Ingo Molnar | [bug, netconsole, SLUB] BUG skbuff_head_cache: Poison overwritten |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: Possible regression in HTB |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
