Re: Terminal issues in fresh install

2008-01-07 Thread Chris Bannister
On Sat, Jan 05, 2008 at 09:31:04AM -0500, Peter Smerdon wrote: Florian Kulzer [EMAIL PROTECTED] writes: On Thu, Jan 03, 2008 at 15:05:10 -0500, Peter Smerdon wrote: [...] Hi, I too have some issue with UTF-8, although I can install and remove software without a problem, my logs get

Re: Terminal issues in fresh install

2008-01-06 Thread Peter Smerdon
Florian Kulzer [EMAIL PROTECTED] writes: The only difference to the setup of your normal user seems to be LANGUAGE. Is there any reason that you reference the iso8859-1 locales there instead of the utf-8 ones? Were the iso8859-1 locales generated on your system? Check if they are listed by

Re: Terminal issues in fresh install

2008-01-05 Thread Peter Smerdon
Florian Kulzer [EMAIL PROTECTED] writes: On Thu, Jan 03, 2008 at 15:05:10 -0500, Peter Smerdon wrote: [...] Hi, I too have some issue with UTF-8, although I can install and remove software without a problem, my logs get filled with perl warnings about locales. If you want help with that

Re: Terminal issues in fresh install

2008-01-05 Thread Florian Kulzer
On Sat, Jan 05, 2008 at 09:31:04 -0500, Peter Smerdon wrote: Florian Kulzer writes: On Thu, Jan 03, 2008 at 15:05:10 -0500, Peter Smerdon wrote: [...] Hi, I too have some issue with UTF-8, although I can install and remove software without a problem, my logs get filled with perl

Re: Terminal issues in fresh install

2008-01-05 Thread Peter Smerdon
Florian Kulzer [EMAIL PROTECTED] writes: Maybe the locale variables are not properly defined for root. What do you get if you run su - -c locale (Or log in as root on the console and check the locale output then. If you normally use su without the - option or sudo to do your root work

Re: Terminal issues in fresh install

2008-01-05 Thread Florian Kulzer
On Sat, Jan 05, 2008 at 15:22:13 -0500, Peter Smerdon wrote: Florian Kulzer writes: Maybe the locale variables are not properly defined for root. What do you get if you run su - -c locale (Or log in as root on the console and check the locale output then. If you normally use su

Re: Terminal issues in fresh install

2008-01-04 Thread Daniel Burrows
On Thu, Jan 03, 2008 at 03:05:10PM -0500, Peter Smerdon [EMAIL PROTECTED] was heard to say: Hi, I too have some issue with UTF-8, although I can install and remove software without a problem, my logs get filled with perl warnings about locales. Which logs? Terminal output?

Re: Terminal issues in fresh install

2008-01-04 Thread Florian Kulzer
On Thu, Jan 03, 2008 at 15:05:10 -0500, Peter Smerdon wrote: [...] Hi, I too have some issue with UTF-8, although I can install and remove software without a problem, my logs get filled with perl warnings about locales. If you want help with that then we need to see the warning messages.

Re: Terminal issues in fresh install

2008-01-04 Thread Chris Bannister
On Wed, Jan 02, 2008 at 09:45:06PM -0800, Daniel Burrows wrote: On Thu, Jan 03, 2008 at 01:50:42PM +1300, Chris Bannister [EMAIL PROTECTED] was heard to say: On Mon, Dec 31, 2007 at 05:19:52PM -0800, Daniel Burrows wrote: I'd guess that the locale of the workstation is relevant here.

SOLVED: Reconfiguring package configuration interface (was Re: Terminal issues in fresh install)

2008-01-03 Thread Dave Sherohman
OK, my questions on mutt and the en_US.UTF-8 package have been answered pretty thoroughly (thanks, all!), but nobody's touched on my other question. Just to get the answer into the archive for the sake of others who may have the same question (or to remind myself in a couple years...) now that

Re: Terminal issues in fresh install

2008-01-03 Thread Peter Smerdon
Daniel Burrows [EMAIL PROTECTED] writes: btw, my locale(1) outputs: [EMAIL PROTECTED] locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=en_US.UTF-8

Re: Terminal issues in fresh install

2008-01-02 Thread Thomas Dickey
David [EMAIL PROTECTED] wrote: Thomas Dickey wrote: Daniel Burrows [EMAIL PROTECTED] wrote: IIRC there was a situation a few years ago where you had to install a Unicode-enabled xterm, pass -u, or both. Sarge dates to 2005; I'm sure that there were X terminals in 2005 that could handle

Re: Terminal issues in fresh install

2008-01-02 Thread Chris Bannister
On Mon, Dec 31, 2007 at 05:19:52PM -0800, Daniel Burrows wrote: I'd guess that the locale of the workstation is relevant here. Your terminal is going to be running in your locale (you didn't mention if was the system console or an X terminal, but I assume an X terminal), and so it won't

Re: Terminal issues in fresh install

2008-01-02 Thread Daniel Burrows
On Thu, Jan 03, 2008 at 01:50:42PM +1300, Chris Bannister [EMAIL PROTECTED] was heard to say: On Mon, Dec 31, 2007 at 05:19:52PM -0800, Daniel Burrows wrote: I'd guess that the locale of the workstation is relevant here. Your terminal is going to be running in your locale (you didn't

Re: Terminal issues in fresh install

2008-01-01 Thread Dave Sherohman
On Mon, Dec 31, 2007 at 05:19:52PM -0800, Daniel Burrows wrote: On Mon, Dec 31, 2007 at 06:23:52PM -0600, Dave Sherohman [EMAIL PROTECTED] was heard to say: Is it significant that the old machine was using the basic en_US locale or that I've been accessing both of them via ssh from a

Re: Terminal issues in fresh install

2008-01-01 Thread Daniel Burrows
On Tue, Jan 01, 2008 at 12:48:04PM -0600, Dave Sherohman [EMAIL PROTECTED] was heard to say: On Mon, Dec 31, 2007 at 05:19:52PM -0800, Daniel Burrows wrote: On Mon, Dec 31, 2007 at 06:23:52PM -0600, Dave Sherohman [EMAIL PROTECTED] was heard to say: Is it significant that the old machine

Re: Terminal issues in fresh install

2008-01-01 Thread Sven Joachim
On 2008-01-01 20:57 +0100, Daniel Burrows wrote: Note that just changing the environment variable inside the terminal won't help -- it's the terminal that needs to interpret those sequences, so you have to run *the terminal itself* in the new locale. Some terminals also allow to change the

Re: Terminal issues in fresh install

2008-01-01 Thread Thomas Dickey
Daniel Burrows [EMAIL PROTECTED] wrote: IIRC there was a situation a few years ago where you had to install a Unicode-enabled xterm, pass -u, or both. Sarge dates to 2005; I'm sure that there were X terminals in 2005 that could handle UTF-8, but I don't know if the default xterm did.

Re: Terminal issues in fresh install

2008-01-01 Thread Thomas Dickey
Sven Joachim [EMAIL PROTECTED] wrote: On 2008-01-01 20:57 +0100, Daniel Burrows wrote: Note that just changing the environment variable inside the terminal won't help -- it's the terminal that needs to interpret those sequences, so you have to run *the terminal itself* in the new locale.

Re: Terminal issues in fresh install

2008-01-01 Thread David
Thomas Dickey wrote: Daniel Burrows [EMAIL PROTECTED] wrote: IIRC there was a situation a few years ago where you had to install a Unicode-enabled xterm, pass -u, or both. Sarge dates to 2005; I'm sure that there were X terminals in 2005 that could handle UTF-8, but I don't know if the

Terminal issues in fresh install

2007-12-31 Thread Dave Sherohman
Greetings, all! I've just moved over from an ancient self-hosted Debian box onto some more modern hardware and things are going mostly smoothly, but I'm having some issues with mutt's thread indicators (extended-ASCII arrows) displaying improperly. I've double-checked that I've got all locale

Re: Terminal issues in fresh install

2007-12-31 Thread Daniel Burrows
On Mon, Dec 31, 2007 at 06:23:52PM -0600, Dave Sherohman [EMAIL PROTECTED] was heard to say: Is it significant that the old machine was using the basic en_US locale or that I've been accessing both of them via ssh from a workstation with its locale set to C? I'd guess that the locale of the