Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3DC87914.5070001@di.fc.ul.pt> Date: Wed, 06 Nov 2002 02:06:12 +0000 From: =?ISO-8859-1?Q?Jo=E3o_Martins?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Trouble with international chars in bash (yes I set up .inputrc) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 06 Nov 2002 02:05:02.0240 (UTC) FILETIME=[EAB83A00:01C28538] Hi. I'm having trouble displaying international charecters in bash. I'm using the latest cygwin (1.3.14-1), on Windows XP Pro, with latest MS updates applied. I've setup my .inputrc as the faq said: set meta-flag on set convert-meta off set output-meta on But bash still doesn't display international characters properly. Instead it apparently displays the char's scancode. For intance, when I press "ç", I get "\347" on the bash prompt. Curiously, other programs seem to work fine: I can use international chars on 'vi' with no problem. If I then set the LESSCHARSET env. var to latin1, I can see (using 'less') the resulting file with no problems as well. Using 'cat' on that file, however, displays garbage characters. If I remove the .inputrc file, bash just beeps at my attempts to use accented/international chars, as normal, so the options are doing something, just not what was expected :) Has anyone else has seen/fixed this problem ? -- ./João -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/