From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21816 invoked by alias); 23 Sep 2009 12:35:05 -0000 Received: (qmail 21808 invoked by uid 22791); 23 Sep 2009 12:35:05 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-qy0-f172.google.com (HELO mail-qy0-f172.google.com) (209.85.221.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 Sep 2009 12:35:01 +0000 Received: by qyk2 with SMTP id 2so515762qyk.21 for ; Wed, 23 Sep 2009 05:34:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.19.21 with SMTP id y21mr849519qca.27.1253709299845; Wed, 23 Sep 2009 05:34:59 -0700 (PDT) In-Reply-To: <20090923120154.GY20981@calimero.vinschen.de> 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> Date: Wed, 23 Sep 2009 12:35:00 -0000 Message-ID: <416096c60909230534g44e80d44t66b18d981b4e3a40@mail.gmail.com> Subject: Re: [1.7] Invalid UTF8 while creating a file -> cannot delete? From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-09/txt/msg00586.txt.bz2 2009/9/23 Corinna Vinschen: > I have a local patch ready to use the ANSI codepage by default in the > "C" locale. =C2=A0It appears to work nicely and has the additional positi= ve > 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. Andy -- 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