X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=BAYES_00,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Ross Smith Subject: Re: [1.7] Invalid UTF8 while creating a file -> cannot delete? Date: Thu, 24 Sep 2009 09:30:28 +1200 Lines: 21 Message-ID: References: <416096c60909101512l6e42ab72l4ba5fd792363eefd@mail.gmail.com> <20090921161014.GI20981@calimero.vinschen.de> <416096c60909211154u5ddd5869v986011aa4ee13d57@mail.gmail.com> <20090922094523.GR20981@calimero.vinschen.de> <416096c60909220912s5dd749bh5cfeb670b0e78c7a@mail.gmail.com> <20090922170709.GV20981@calimero.vinschen.de> <20090923120154.GY20981@calimero.vinschen.de> <416096c60909230534g44e80d44t66b18d981b4e3a40@mail.gmail.com> <20090923124307.GD20981@calimero.vinschen.de> <20090923133939.GE20981@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) In-Reply-To: <20090923133939.GE20981@calimero.vinschen.de> X-IsSubscribed: yes 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 Corinna Vinschen wrote: > > However, if we default to UTF-8 for a subset of languages anyway, it > gets even more interesting to ask, why not for all languages? Isn't it > better in the long run to have the same default for all Cygwin > installations? > > I'm really wondering if we shouldn't simply default to UTF-8 as charset > throughout, in the application, the console, and for the filename > conversion. Yes, not all applications will work OOTB with chars > 0x7f, > but it was always a bug to make any assumptions for non-ASCII chars > in the C locale. Applications can be fixed, right? In support of this plan, it occurs to me that any command line applications that don't speak UTF-8 would presumably be showing the same behaviour on Linux (e.g. odd column widths). Since one of Cygwin's main goals is providing a Linux-like environment on Windows, I don't think Cygwin developers should feel obliged to go out of their way to do _better_ than Linux in this regard. -- Ross Smith -- 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