From owner-freebsd-questions@FreeBSD.ORG Sun Feb 3 17:14:29 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4D3006CF; Sun, 3 Feb 2013 17:14:29 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 15189171; Sun, 3 Feb 2013 17:14:28 +0000 (UTC) Received: from r56.edvax.de (port-92-195-8-191.dynamic.qsc.de [92.195.8.191]) by mx02.qsc.de (Postfix) with ESMTP id 27615248A9; Sun, 3 Feb 2013 18:14:28 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id r13HEUlf002027; Sun, 3 Feb 2013 18:14:30 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sun, 3 Feb 2013 18:14:30 +0100 From: Polytropon To: Andre Goree Subject: Re: [kde-freebsd] tmux and konsole characters Message-Id: <20130203181430.53e88178.freebsd@edvax.de> In-Reply-To: <510E9638.5010305@drenet.info> References: <510D35F8.8010004@drenet.info> <1359896784.8510.140661186191169.24EAC5DA@webmail.messagingengine.com> <510E9638.5010305@drenet.info> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Schaich Alonso , kde@freebsd.org, freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 17:14:29 -0000 On Sun, 03 Feb 2013 11:54:16 -0500, Andre Goree wrote: > On a related note, I guess I can set LANG=en_US.UTF-8 in my .bashrc and > have that as my default, no? As far as I remember, login.conf is the file to set this, but you can basically set environmental variables wherever you want. For example, I have a system where I set them globally in the C-Shell configuration, so all shells (even non-csh-shells like bash) inherit the settings. Example from /etc/csh.cshrc: setenv LC_ALL en_US.UTF-8 setenv LC_MESSAGES en_US.UTF-8 setenv LC_COLLATE de_DE.UTF-8 setenv LC_CTYPE de_DE.UTF-8 setenv LC_MONETARY de_DE.UTF-8 setenv LC_NUMERIC de_DE.UTF-8 setenv LC_TIME de_DE.UTF-8 setenv LANG de_DE.UTF-8 Note that this creates a "settings conglomerate" from english and german settings which looks stupid, but works (and is therefor intended, or at least accepted as being established). :-) Note the correct language prefix: en_US (as there's also en_GB). > Any nuances on en_US.UTF-8 vs. ISO8859? As soon as you have "non-standard" characters (like german umlauts) encoded in ISO8859-1 (the default for this region) they won't show up properly in UTF-8 (just as UTF-8 encoded umlauts will not show up properly in a ISO8859-1 terminal session). > I've never really ever needed to deal with locales before, but I believe > UTF-8 offers more characters, no? It offers many more, and especially if you're dealing with "inter- national documents", it seems to be the best way to go at the moment. For example, I had to work on a document containing german umlauts and chinese characters, so UTF-8 was the solution to have all of them properly displayed and editable. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...