This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Bag LANG setting?
- From: Andy Koppe <andy dot koppe at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 14 Jan 2010 20:31:00 +0000
- Subject: Re: Bag LANG setting?
- References: <CBF40C8AC4CA41E0BBC664570D4F07C8@phoenix>
2010/1/14 Jason Pyeron <jpyeron@pdinc.us>:
> When doing man grep it blurted out many <##> hex codes. If I unset LANG, LANGVAR I get extended ascii. I am using teraterm to connect via ssh.
What's 'extended ascii'?
You need to ensure that your terminal is set to the same character set
as Cygwin. The second of your 'man grep' examples with the funny
characters is due to using UTF-8 for Cygwin while the terminal is
using ISO-8859-15 or similar. I don't know how you'd get it to produce
the <##> hex codes in the first example.
> LANG=en_US.iso885915
That's not a valid locale. Should be en_US.ISO-8859-15
> LANGVAR=en_US.UTF-8
What's LANGVAR? Cygwin won't care about it.
> LC_CTYPE=en_US.UTF-8
This overrides the charset in your LANG setting above. Best just use
LANG, unless you know what you're doing.
> I cannot remember when the man output was last formatted correctly. Any advise on where to check next?
>
> $ uname -a
> CYGWIN_NT-5.1 phoenix 1.7.0(0.212/5/3) 2009-08-20 10:56 i686 Cygwin
Looks like you could do with an update.
Andy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple