X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 14 May 2009 16:42:31 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [1.7] Proposal: the filename encoding in C locale uses UTF-8 instead of SO/UTF-8 Message-ID: <20090514144231.GA19217@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3f0ad08d0905121029j119c8a7ep41d3a261d8bea338@mail.gmail.com> <20090512173741.GZ21324@calimero.vinschen.de> <20090513142953.GI21324@calimero.vinschen.de> <3f0ad08d0905130903o5cf0330enc8025bc92e94225c@mail.gmail.com> <20090513164526.GO21324@calimero.vinschen.de> <3f0ad08d0905131025j3f9a23c4k8c940dee496ee6fd@mail.gmail.com> <20090513174114.GU21324@calimero.vinschen.de> <3f0ad08d0905131213k6c8f1b25h3322f20b5bb80631@mail.gmail.com> <20090513194645.GV21324@calimero.vinschen.de> <3f0ad08d0905140706y3c039ceq707d6a5c79907f21@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3f0ad08d0905140706y3c039ceq707d6a5c79907f21@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On May 14 23:06, IWAMURO Motonori wrote: > 2009/5/14 Corinna Vinschen : > > I see a couple of potential problems. > > What problems are those? I have no example off-hand. When I thought about it I always got sick thinking about scenarios where the library is using, say, UTF-8, and the application is using SJIS, and what happens to the filenames in this case. In theory the lib should provide what the application thinks it right. > > And have some time to discuss whether these are something the > > user can or even should fix or workaround alone. > > I think that the application that use locale by the environment > variable and the application that use no locale should be able to read > and write the same byte sequence. Ok, you got as point there. Assuming we leave out any application which deliberately uses a non-"C" locale which differs from the setting in the environment. Then we're getting into trouble. If Cygwin uses internally always the environment setting, we have a valid, identical byte stream for all applications using setlocale(LC_ALL, ""), *and* for non locale-aware applications. But if the application uses a deliberately different setting via setlocale, ..., hmm. It should get what it asks for. Maybe, you're right. I have to test this a bit. Thanks for your input, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/