From: KOBAYASHI Yasuhiro <kobayays@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: Build error with _UNICODE on w32.
Date: Tue, 20 May 2008 15:44:10 +0900 [thread overview]
Message-ID: <4v7idpbhl1.fsf@otsukakj.co.jp> (raw)
In-Reply-To: uej81hvwt.fsf@gnu.org
In message Re: Build error with _UNICODE on w32.
on Sat, 17 May 2008 17:01:22 +0300
Eli Zaretskii <eliz@gnu.org> wrote:
> I wasn't aware this is even supported. It is certainly not
> used/tested enough to be recommended for general use. We don't
> consistently use the TCHAR type or any other types that magically
> switch to wchar_t under UNICODE compilation, and freely mix text
> strings returned from Windows APIs with plain `char *' pointers and
> strings. To get Emacs support the Unicode Windows APIs will take a
> major overhaul of the code.
> What did you expect to get with the -D_UNICODE switch that you don't
> get without it?
I was trying to maintain the IME-patch on w32. I need it to
input the unicode character.
The following is ad hoc one.
w32.c:
@@ -773,7 +773,7 @@
dflt_passwd.pw_gid = get_rid (group_token.PrimaryGroup);
dlength = sizeof (domain);
if (lookup_account_sid (NULL, group_token.PrimaryGroup,
- gname, &glength, NULL, &dlength,
+ gname, &glength, domain, &dlength,
&user_type))
strcpy (dflt_group_name, gname);
}
--
KOBAYASHI Yasuhiro <kobayays@gmail.com>
next prev parent reply other threads:[~2008-05-20 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 4:49 Build error with _UNICODE on w32 KOBAYASHI Yasuhiro
2008-05-17 7:19 ` Eli Zaretskii
2008-05-17 13:33 ` KOBAYASHI Yasuhiro
2008-05-17 14:01 ` Eli Zaretskii
2008-05-20 6:44 ` KOBAYASHI Yasuhiro [this message]
2008-05-20 9:14 ` Jason Rumney
2008-05-20 18:20 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4v7idpbhl1.fsf@otsukakj.co.jp \
--to=kobayays@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-pretest-bug@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).