Thread: Perl locale
View Single Post
  #4   (View Single Post)  
Old 9th January 2009
lvlamb's Avatar
lvlamb lvlamb is offline
Real Name: Louis V. Lambrecht
Spam Deminer
 
Join Date: May 2008
Location: .be
Posts: 221
Default

For one, there is no UTF-8 support at the OS level on OpenBSD.
There are UTF-8 /usr/share/locale directories which are empty, hence fallback to C, but this prevent error messages.

For the LC_ALL=C fallback, in the LInux days when they were adapting UTF-8, I used to set the environment to it.
Under OpenBSD default ksh, I often type
env LC_ALL=C [command] [arguments] which does nothing but prevent error messages.

You would set those variables in
~/.profile

Usually (other OSes), the system wide setting would happen in /etc/login.conf
but
as assumption is the mother of all f#ck-ups, checked the manpages and found no indication.
Hence, no answer. I cover my back
Also, don't su but sudo and, in the
/etc/sudoers
uncomment (visudo)
#Defaults:%wheel !env_reset
This would be OK for a one-only sysadmin system.


One of the reasons to use Xorg (/usr/X11R6/share/X11/locale) and UTF-8 aware applications.

Btw, you perfectly can save a file (OS file-system level), with UTF-8 characters in it (application level): UTF-8 aware aplications read it perfectly but the CLI will strip some characters. Just be aware that the CLI shells (OS level) will not do the translation.
Note that this also happens when the filenames have extended ASCII you would read differently under Xorg and the CLI if not set to the same locales|xlocales.

Using OpenBSD as a desktop for some years now, I don't know anymore how mendatory a full UTF-8 support from the OS level up would be vs. keeping the OS in full old plain trusted ASCII-7.
__________________
da more I know I know I know nuttin'
Reply With Quote