delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/12/16/17:40:38

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 16 Dec 2004 17:40:16 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Lino Miguel Martins Tinoco <lino-m-tinoco AT telecom DOT pt>
cc: cygwin AT cygwin DOT com
Subject: Re: Non-US keyboard (PT) bash problem
In-Reply-To: <9D3B864C501E024B86A5ABF53972A66A4494BA@COMTVLEX02.ptcom.corppt.com>
Message-ID: <Pine.GSO.4.61.0412161733470.2298@slinky.cs.nyu.edu>
References: <9D3B864C501E024B86A5ABF53972A66A4494BA AT COMTVLEX02 DOT ptcom DOT corppt DOT com>
MIME-Version: 1.0

------_=_NextPart_001_01C4E36B.D8A87205
Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1
Content-Transfer-Encoding: 8BIT
Content-ID: <Pine DOT GSO DOT 4 DOT 61 DOT 0412161733472 DOT 2298 AT slinky DOT cs DOT nyu DOT edu>

On Thu, 16 Dec 2004, Lino Miguel Martins Tinoco wrote:

> Hi!
>
> I can't have special characters displayed correctly on bash (ç, Ç and
> accents). They are displayed as ? when I do a ls but they get displayed
> correctly if I pipe the results or send them to a file. On command line
> they are displayed as the respective octal value (ç is displayed as
> \347). Before I try the set meta-flag solution, bash was interpreting
> some of these symbols (hitting ç twice gave me an ls).

For 'ls' you may wish to use the --show-control-chars flag.  For bash (or,
rather, readline), you will need all four of

set meta-flag on
set convert-meta off
set input-meta on
set output-meta on

(see <http://www.cygwin.com/faq/faq_3.html#SEC46>), and/or the respective
manpages.

> Also tried codepage:oem, but didn't worked. On a DOS box this characters
> are displayed ok. They are also displayed ok on any editor (vi, emacs,
> ...). This happens on console window and xterm or rxvt.

When you say "DOS box", I presume you mean the actual Windows Command
Prompt window, so looks like your problem is with bash.  Since you seem to
have the same behavior in console, xterm, and rxvt, this doesn't look like
a font issue.  If the above doesn't help, please post the exact steps to
reproduce the problem.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

------_=_NextPart_001_01C4E36B.D8A87205
Content-Type: text/plain; charset=us-ascii

--
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/
------_=_NextPart_001_01C4E36B.D8A87205--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019