From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?
Date: Wed, 23 Sep 2009 12:35:00 -0000 [thread overview]
Message-ID: <416096c60909230534g44e80d44t66b18d981b4e3a40@mail.gmail.com> (raw)
In-Reply-To: <20090923120154.GY20981@calimero.vinschen.de>
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.
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
next prev parent reply other threads:[~2009-09-23 12:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 19:31 Lapo Luchini
2009-09-10 22:12 ` Andy Koppe
2009-09-15 22:38 ` Lapo Luchini
2009-09-21 16:10 ` Corinna Vinschen
2009-09-21 18:54 ` Andy Koppe
2009-09-22 9:45 ` Corinna Vinschen
2009-09-22 16:12 ` Andy Koppe
2009-09-22 17:07 ` Corinna Vinschen
2009-09-23 11:52 ` Andy Koppe
2009-09-23 12:02 ` Corinna Vinschen
2009-09-23 12:35 ` Andy Koppe [this message]
2009-09-23 12:43 ` Corinna Vinschen
2009-09-23 13:39 ` Corinna Vinschen
2009-09-23 21:31 ` Ross Smith
2009-09-25 22:36 ` Robert Pendell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416096c60909230534g44e80d44t66b18d981b4e3a40@mail.gmail.com \
--to=andy.koppe@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).