This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?
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? Â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
>
>
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@elite-systems.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