Message-ID: <45ABC199.3010309@cygwin.com>
Date: Mon, 15 Jan 2007 13:02:01 -0500
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061221 Fedora/1.5.0.9-1.fc4.remi Thunderbird/1.5.0.9 Mnenhy/0.7.4.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: National characters in the command window
References: <004301c738ce$234cc280$3001a8c0 AT Asymmetric>
In-Reply-To: <004301c738ce$234cc280$3001a8c0@Asymmetric>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Enrique Perez-Terron wrote:
> I have a Norwegian keyboard, and when I type the national characters on 
> the command
> line, nothing shows up - that is, the æ (the ae ligature) and å (a with 
> ring above) keys do not
> respond, while the ø (o with slash across) key produces 'o'.  
> Dead-accent key combinations
> produce nothing.  The cursor does not advance.
> 
> I have a file with the ae ligature in the file name. The command "ls | 
> od -t x1" shows that
> character as 0xe6, consistent with latin1 or with cp1252. "ls" to the 
> screen displays the
> file name properly. It seems the problem only affects keyboard input.
> 
> In a regular "dos" cmd window I can type file names with national 
> characters, and list the file
> names.
> 
> The environment vairables LANG and LC_* are not set. I have not found 
> any setting of these
> that make a difference.
> 
> The command
> 
>    chcp.com
> 
> in the bash window returns 437.  In 436, the ae ligature is 0x91.
> 
> In a regular dos cmd window, "dir > dirfile" produces a file that 
> contains cp437 coded file names.
> The ae ligature is 0x91. I determine this by "od < dirfile" in the bash 
> window.
> 
> Using chcp to set codepage 1252 in the bash window makes the ae ligature 
> display as the greek
> mu character when doing "ls" to the screen.  "ls | od" still shows 0xe6 
> (1252) for the ae ligature.
> On input, the o-slash key nno longer produces 'o'. It produces nothing. 
> The cursor does not
> advance.  Starting a new bash process in the same window does not seem 
> to change anything.
> 
> I have found so little about this on the net, that I believe I must be 
> missing something very
> basic in my cygwin installation. Does everybody else have the same problem?
> 
> Is there a good description anywhere of how these things work?


Does <http://cygwin.com/faq/faq-nochunks.html#faq.using.unicode> not help?

Have you checked the email archives?  I know this has come up before.


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/