X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Ralf Subject: Re: Internal echo of shell beaves (sometimes) different to external echo Date: Fri, 20 Jul 2012 10:46:33 +0000 (UTC) Lines: 14 Message-ID: References: <50086B4A DOT 6090801 AT laposte DOT net> <20120720082452 DOT GV31055 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 My problem is not that the script is in ISO-8859-1, nor that the strings or ttt.txt are in ISO-8859.1. They have to be in ISO-8859-1 because all my scripts are in ISO-8859-1 and they are used together with Windows-Programs (in the DOS-Box) which read and write only ISO-8851-1. My Problem is to handle in Shell-Scripts strings which are coded in ISO-8851 (and line-endings which depend on relative/absolute filenames, mounting and so on) without rewriting all the stuff. So what't the best setting in cygwin to echo ISO-88591? I still don't unterstand why the internal echo behaves in a different way from the external echo. -- 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