X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 19 Mar 2009 20:22:29 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Q: Is anybody here using the CYGWIN=codepage:oem setting? Message-ID: <20090319192229.GC9322@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090319130909 DOT GZ9322 AT calimero DOT vinschen DOT de> <49C281F7 DOT 6080602 AT acm DOT org> <20090319181323 DOT GB1868 AT calimero DOT vinschen DOT de> <49C29366 DOT 8080708 AT acm DOT org> <20090319192031 DOT GB9322 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090319192031.GB9322@calimero.vinschen.de> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mar 19 20:20, Corinna Vinschen wrote: > On Mar 19 11:48, David Rothenberger wrote: > >> Not exactly. However, assuming you have a file using characters which > >> are not in your current ANSI codeset, then you could only manipulate > >> that file when setting LANG="xx_YY.UTF-8", and only in applications > >> which call setlocale(). > > > > I have no idea whether du calls setlocale() or not. I think you're > > saying that today, with codepage:utf8, it is able to get sizes for files > > using non-ANSI characters, but if codepage is removed, it would not be > > able to do so unless it called setlocale(). Is that right? > > Right. ...unless Cygwin itself would call setlocale(). Corinna -- 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/