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 Mail-Followup-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com From: Alejandro Lopez-Valencia Subject: Re: 1.5.7: Problems with german umlauts in bash/rxvt command line Date: Fri, 27 Feb 2004 08:42:57 -0500 Organization: Casa de Cuckoo Lines: 17 Message-ID: References: <20040227084944 DOT GQ2104 AT bln DOT sesa DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet AT sea DOT gmane DOT org Keywords: Has control X-Headers X-Gmane-NNTP-Posting-Host: 200.119.73.50 X-Archive: encrypt Mail-Copies-To: never X-Newsreader: Forte Agent 2.0/32.640 Reply-To: cygwin AT cygwin DOT com On Fri, 27 Feb 2004 12:35:23 +0100, Thorsten Kampe wrote in : > although typing non-ascii characters in a >shell doesn't make sense. The only use is showing files with ls or d - >which is not a shell thing. Really? Say, you use cygwin to do text processing (I do, with the help of a bleeding edge groff), and in a whim you decide to write poetry to your girlfirend. Being a German speaker, you type, e.g., "Lieder_für_meine_geliebte.tr". Did you or did you not need to type high-bit charecters in your shell? (Don't say you type them from within your editor, that's cheating). -- 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/