This explains why apps run straight through putty didn't experience this issue. However when I ran an ncurses app via screen on putty, I experienced a unique set of character mutations. SSH on FreeBSD, on the other hand, gave me its own set of issues, and far more exaggerated ones at that, whether using screen or not. In any event, I don't see as I have any particular need for UTF-8 support anywhere in the system, so I suspect I'll be happy with en_US. I've read that adding LC_COLLATE="C" to /etc/sysconfig/i18n will prevent certain gmake-related issues when specifying LANG=en_US. Does this seem correct? Thanks again to everyone for the insight. armen
------------------------------
Message: 3 Date: Wed, 9 Mar 2005 12:42:00 -0500 (EST) From: "William Hooper" <whooperhsd3@xxxxxxxxxxxxx> Subject: Re: Termcap/Terminfo & Ncurses To: fedora-list@xxxxxxxxxx Message-ID: <2173.12.29.16.103.1110390120.squirrel@xxxxxxxxxxx> Content-Type: text/plain;charset=iso-8859-1
armen said:
Indeed, changing LANG="en_US.UTF-8" to LANG="en_US" seems to fix the screen-via-putty issues.
PuTTY natively supports UTF-8.
http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html#QA.7.18
-- William Hooper
