From: IWAMURO Motonori <deenheart@gmail.com>
To: cygwin@cygwin.com
Subject: Re: The C locale
Date: Thu, 24 Sep 2009 07:03:00 -0000 [thread overview]
Message-ID: <3f0ad08d0909240003j435818e7h6f7cde2e26188f7e@mail.gmail.com> (raw)
In-Reply-To: <416096c60909211420g4ac8ea93l80fc1f00dcd5c0f3@mail.gmail.com>
2009/9/22 Andy Koppe <andy.koppe@gmail.com>:
> Let's use the Windows "ANSI" codepage as the character set for the C
> locale, for both the conversion functions and filenames. This means
> CP1252 on Western systems, CP1251 on Cyrillic ones, CP932 on Japanese
> ones, and so on.
I oppose the approach (the ANSI codepage is used at C locale) because
CP932 (the codepage for Japanese) is hostile to the UNIX-like tools.
The reason is that the CP932 format contains a lot of meta characters
as follows.
single character of CP932:
/[\x00-\x7F\xA0-\xDF]|[\x81-\x9F\xE0-\xFC][\x40-\x7E\x80-\xFC]/
This has a ruined influence to the tools that don't see locale.
--
IWAMURO Motnori <http://vmi.jp/>
--
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-24 7:03 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 16:59 Andy Koppe
2009-08-31 0:53 ` Christopher Faylor
2009-09-02 6:29 ` Andy Koppe
2009-09-02 11:48 ` Eric Blake
2009-09-02 20:10 ` Andy Koppe
2009-09-02 13:56 ` IWAMURO Motonori
2009-09-07 20:08 ` Andy Koppe
2009-09-08 19:35 ` Corinna Vinschen
2009-09-08 20:48 ` Andy Koppe
2009-09-08 21:49 ` Andy Koppe
2009-09-21 10:38 ` Corinna Vinschen
2009-09-21 13:08 ` Lapo Luchini
2009-09-21 14:39 ` Charles Wilson
2009-09-21 21:20 ` Andy Koppe
2009-09-22 5:59 ` Lapo Luchini
2009-09-22 6:23 ` Lapo Luchini
2009-09-22 6:50 ` Andy Koppe
2009-09-22 6:47 ` Andy Koppe
2009-09-22 8:43 ` Lapo Luchini
2009-09-22 12:50 ` Andy Koppe
2009-09-22 16:26 ` Lapo Luchini
2009-09-22 16:49 ` Mark J. Reed
2009-09-22 17:04 ` Lapo Luchini
2009-09-22 22:11 ` Thorsten Kampe
2009-09-23 5:12 ` Lapo Luchini
2009-09-23 9:04 ` Thorsten Kampe
2009-09-23 10:48 ` Lapo Luchini
2009-09-23 12:04 ` Andy Koppe
2009-09-23 15:16 ` Mark J. Reed
2009-09-24 7:58 ` Thorsten Kampe
2009-09-24 7:03 ` IWAMURO Motonori [this message]
2009-09-24 7:34 ` Corinna Vinschen
2009-09-24 9:39 ` IWAMURO Motonori
2009-09-24 9:57 ` Corinna Vinschen
2009-09-24 10:00 ` Corinna Vinschen
2009-09-26 9:15 ` Corinna Vinschen
2009-09-27 3:21 ` IWAMURO Motonori
2009-09-28 16:03 ` IWAMURO Motonori
2009-09-28 16:16 ` Corinna Vinschen
2009-09-29 0:23 ` wynfield
2009-09-29 4:04 ` Andy Koppe
2009-09-29 13:55 ` IWAMURO Motonori
2009-09-29 4:27 ` Andy Koppe
2009-09-29 7:03 ` Corinna Vinschen
2009-09-29 10:55 ` Lapo Luchini
2009-09-29 11:12 ` Thomas Wolff
2009-09-29 12:12 ` Corinna Vinschen
2009-09-29 14:30 ` IWAMURO Motonori
2009-09-29 14:13 ` IWAMURO Motonori
2009-09-29 14:55 ` Corinna Vinschen
2009-09-27 3:44 ` IWAMURO Motonori
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=3f0ad08d0909240003j435818e7h6f7cde2e26188f7e@mail.gmail.com \
--to=deenheart@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).