X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 23 Sep 2009 14:43:07 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [1.7] Invalid UTF8 while creating a file -> cannot delete? Message-ID: <20090923124307.GD20981@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com 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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <416096c60909230534g44e80d44t66b18d981b4e3a40@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 Sep 23 13:34, Andy Koppe wrote: > 2009/9/23 Corinna Vinschen: > > I have a local patch ready to use the ANSI codepage by default in the > > "C" locale.  It appears to work nicely and has the additional positive > > side effect to simplify the code in a few places. > > > > If I only new that eastern language users could happily live with > > this change as well! > > Here's an idea to circumvent the DBCS troubles: default to UTF-8 when > no charset is specified in the locale and the ANSI charset isn't > singlebyte. > > Based on the following grounds: > - Full CJK support (and more) out of the box. > - DBCSs can't have worked very well in 1.5 in the first place, because > the shell and most applications weren't aware of double-byte > characters. Hence backward compatibility is less of an issue here. > - Applications that don't (yet) work with UTF-8 are also unlikely to > work correctly with DBCSs. > - Iwamuro Motonori asked for it. Yeah, I was tinkering with this idea, too, but it's much more tricky to implement. I'll think about it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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