From: Dmitry Potapov <dpotapov@gmail.com>
To: John Dlugosz <JDlugosz@tradestation.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH] Windows: Assume all file names to be UTF-8 encoded.
Date: Wed, 4 Mar 2009 00:02:40 +0300 [thread overview]
Message-ID: <37fcd2780903031302m5f98fe71u8bdb23f90a8df82a@mail.gmail.com> (raw)
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E709F077AC@EXCHANGE.trad.tradestation.com>
On Tue, Mar 3, 2009 at 11:39 PM, John Dlugosz <JDlugosz@tradestation.com> wrote:
>
> Now, the default when a program starts is to use the "C" locale. The
> locale argument to setlocale can take a form ".code_page", so calling
>
> setlocale (LC_CTYPE, ".65001");
>
> should do the trick. Assuming, that is, that you don't hit macros that
> assume that characters are never multibyte. So define the preprocessor
> symbol _MBCS when you compile.
If Microsoft fixed the problem with UTF-8 support in C runtime, it is
a really good
news, because setlocale did not work not so long time ago:
http://blogs.msdn.com/michkap/archive/2006/03/13/550191.aspx
As to Win32 API, it has always worked correctly with UTF-8... In fact, the
documentation of GetOEMCP function goes as far as recommending
to use UTF-8 or UTF-16: "For the most consistent results, applications should
use Unicode, such as UTF-8 or UTF-16, instead of a specific code page.
So it would be great if Git supported UTF-8 on Windows (as an option), but it
is not my itch right now....
Dmitry
next prev parent reply other threads:[~2009-03-03 21:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 20:39 [RFC PATCH] Windows: Assume all file names to be UTF-8 encoded John Dlugosz
2009-03-03 21:02 ` Dmitry Potapov [this message]
2009-03-03 21:56 ` John Dlugosz
-- strict thread matches above, loose matches on Subject: below --
2009-03-03 19:36 John Dlugosz
2009-03-03 18:25 John Dlugosz
2009-03-04 10:53 ` Peter Krefting
2009-03-04 19:34 ` John Dlugosz
2009-03-02 8:47 Peter Krefting
2009-03-02 10:30 ` Johannes Sixt
2009-03-02 10:46 ` Peter Krefting
2009-03-02 10:56 ` Johannes Schindelin
2009-03-02 12:03 ` Peter Krefting
[not found] ` <a2633edd0903020512u5682e9am203f0faccd0acf6a@mail.gmail.com>
2009-03-02 13:57 ` Peter Krefting
2009-03-02 14:29 ` Thomas Rast
2009-03-02 20:41 ` Peter Krefting
2009-03-03 7:56 ` Lars Noschinski
2009-03-03 11:54 ` Peter Krefting
2009-03-03 16:29 ` Lars Noschinski
2009-03-03 20:59 ` Robin Rosenberg
2009-03-03 9:47 ` Dmitry Potapov
2009-03-03 11:48 ` Peter Krefting
2009-03-03 17:13 ` Dmitry Potapov
2009-03-04 10:51 ` Peter Krefting
2009-03-04 14:18 ` Dmitry Potapov
2009-03-02 12:34 ` Johannes Sixt
2009-03-02 13:12 ` Peter Krefting
2009-03-02 19:58 ` Robin Rosenberg
2009-03-02 20:52 ` Peter Krefting
2009-03-02 21:21 ` Robin Rosenberg
2009-03-03 5:51 ` Peter Krefting
2009-03-03 9:43 ` Dmitry Potapov
2009-03-03 11:56 ` Peter Krefting
2009-03-07 10:38 ` Robin Rosenberg
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=37fcd2780903031302m5f98fe71u8bdb23f90a8df82a@mail.gmail.com \
--to=dpotapov@gmail.com \
--cc=JDlugosz@tradestation.com \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).