X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <h9e41n$4fn$1@ger.gmane.org>
References: <416096c60909101512l6e42ab72l4ba5fd792363eefd AT mail DOT gmail DOT com> 	 <416096c60909211154u5ddd5869v986011aa4ee13d57 AT mail DOT gmail DOT com> 	 <20090922094523 DOT GR20981 AT calimero DOT vinschen DOT de> 	 <416096c60909220912s5dd749bh5cfeb670b0e78c7a AT mail DOT gmail DOT com> 	 <20090922170709 DOT GV20981 AT calimero DOT vinschen DOT de> 	 <20090923120154 DOT GY20981 AT calimero DOT vinschen DOT de> 	 <416096c60909230534g44e80d44t66b18d981b4e3a40 AT mail DOT gmail DOT com> 	 <20090923124307 DOT GD20981 AT calimero DOT vinschen DOT de> 	 <20090923133939 DOT GE20981 AT calimero DOT vinschen DOT de> 	 <h9e41n$4fn$1 AT ger DOT gmane DOT org>
Date: Fri, 25 Sep 2009 18:36:02 -0400
Message-ID: <a13b5a590909251536x6b50870fj3519835c471c68fd@mail.gmail.com>
Subject: Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?
From: Robert Pendell <shinji AT elite-systems DOT org>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Wed, Sep 23, 2009 at 5:30 PM, Ross Smith wrote:
> 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? =C2=A0Isn'=
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. =C2=A0Yes, 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. =C2=A0Applications 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
>
>

I don't have anything to add on the technical side of things but I
will note that most linux distributions have been defaulting to UTF-8
lately.  I think it would be highly appropriate to default to UTF-8 in
cygwin.

Robert Pendell
shinji AT elite-systems DOT org

"A perfect world is one of chaos."

Thawte Web of Trust Notary
CAcert Assurer

--
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