View Single Post
Old 6th September 2016
shep shep is offline
Real Name: Scott
Arp Constable
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,194

The FAQ has sections on remapping keyboards and localization.
The level of UTF-8 support and the default encoding configuration vary greatly with the program or library. For example, xterm(1) has full UTF-8 support enabled by default, while the regular expression library does not have any UTF-8 support yet.

To use the Unicode character set in UTF-8 encoding whereever supported, set the LC_CTYPE environment variable to the value en_US.UTF-8:

If logging in via xdm(1), add export LC_CTYPE="en_US.UTF-8" to your ~/.xsession before starting the window manager. See customizing X for more details.
If logging in via the text console, add export LC_CTYPE="en_US.UTF-8" to your ~/.profile. The text console's UTF-8 support is a work in progress, and some non-ASCII characters may not display properly.
When logging into remote systems with ssh(1), the LC_CTYPE environment variable is not propagated, and you have to make sure that the local terminal is set to the character encoding used by the remote server before starting the ssh(1) client program. If that encoding is unknown or unsupported by OpenBSD, make sure you use the default xterm(1) configuration and set LC_CTYPE=en_US.UTF-8 in the remote shell after connecting.
The OpenBSD base system completely ignores all locale-related environment variables except LC_CTYPE; even LC_ALL and LANG only affect the character encoding. Some ports may respect other LC_* variables, but using them or setting LC_CTYPE to any value other than C, POSIX or en_US.UTF-8 is not recommended.
Reply With Quote