From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Let's use the Win32 API more precisely
Date: Thu, 27 Jun 2019 02:37:17 -0700 (PDT) [thread overview]
Message-ID: <pull.147.git.gitgitgadget@gmail.com> (raw)
For many Win32 functions, there actually exist two variants: one that takes
const char * ("ANSI", meaning the current code page) and wchar_t *
("Unicode", i.e. UTF-16, at least for all practical matters).
These functions have "A" and "W" suffixes, respectively, e.g.
GetFileAttributesW(). The symbols without this suffix are #defined to the
*W() versions if the constant UNICODE is defined before including the
Windows headers, and to *A() otherwise.
Let's not rely on this constant, but explicitly say what we want: we want
the Unicode versions, as they seem to be used by the ANSI flavor anyway.
Johannes Schindelin (2):
mingw: get pw_name in UTF-8 format
mingw: use Unicode functions explicitly
compat/mingw.c | 12 +++++++++---
compat/poll/poll.c | 2 +-
compat/winansi.c | 10 ++++++----
3 files changed, 16 insertions(+), 8 deletions(-)
base-commit: aa25c82427ae70aebf3b8f970f2afd54e9a2a8c6
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-147%2Fdscho%2Fansi-unicode-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-147/dscho/ansi-unicode-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/147
--
gitgitgadget
next reply other threads:[~2019-06-27 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 9:37 Johannes Schindelin via GitGitGadget [this message]
2019-06-27 9:37 ` [PATCH 1/2] mingw: get pw_name in UTF-8 format Johannes Schindelin via GitGitGadget
2019-07-04 20:13 ` Beat Bolli
2019-07-04 21:52 ` Johannes Schindelin
2019-07-04 21:54 ` Beat Bolli
2019-06-27 9:37 ` [PATCH 2/2] mingw: use Unicode functions explicitly Johannes Schindelin via GitGitGadget
2019-06-27 17:26 ` Eric Sunshine
2019-06-27 18:54 ` Johannes Schindelin
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=pull.147.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).