unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Fujii Hironori <fujii.hironori@gmail.com>
Cc: 11732-done@debbugs.gnu.org
Subject: bug#11732: 24.1; Microsoft IME Japanese input problem
Date: Thu, 19 Feb 2015 13:44:29 +0200	[thread overview]
Message-ID: <8361ay3z36.fsf@gnu.org> (raw)
In-Reply-To: <CALus1PmqiC8TnQTfcpVFD5ObjqbK_4hkOczRKmG1=+mkWXUHWQ@mail.gmail.com>

> Date: Thu, 19 Feb 2015 19:40:18 +0900
> From: Fujii Hironori <fujii.hironori@gmail.com>
> 
> >> | Remarks
> >> |
> >> | This message is a notification to an IME window to open its
> >> | composition window. An application should process this message if it
> >> | displays composition characters itself.
> >> |
> >> | If an application has created an IME window, it should pass this
> >> | message to that window. The DefWindowProc function processes the
> >> | message by passing it to the default IME window.
> >
> > Yes, I've read that, but it's still not clear to me what that mean in
> > practice.  Are you saying that ImmSetCompositionWindow only sets the
> > position of the composition window, but it will not be shown unless we
> > pass WM_IME_STARTCOMPOSITION to DefWindowProc?
> 
> Yes, I am.
> 
> > In that case, how will
> > Windows know that the composition window we positioned is "the default
> > IME window"?
> 
> I don't understand what this means.
> The default IME window is not a composition window, but opens its
> composition window.
> 
> In SDK document, there are some hints what the default IME window is.
> 
> https://msdn.microsoft.com/en-us/library/windows/desktop/dd318561(v=vs.85).aspx
> 
> | The operating system creates a default IME window for every
> | thread. The window is created based on the IME class.
> 
> https://msdn.microsoft.com/en-us/library/windows/desktop/dd318170(v=vs.85).aspx
> 
> | IME Window Class
> |
> | The IME window class is a predefined system global class that defines
> | the appearance and behavior of the standard IME windows. The class is
> | similar to common control classes in that the application creates a
> | window of this class by using the CreateWindowEx function. Like static
> | controls, an IME window does not respond to user input by
> | itself. Instead, it notifies the IME of user input actions and
> | processes control messages sent to it by the IME or applications to
> | carry out a response to the user action.
> 
> > Or are you saying we should be calling ImmSetCompositionWindow at all?
> > That call was introduced as result of solving bugs #2570 and #2569, so
> > I think the call or its equivalent should stay.
> 
> I don't understand what this means.
> ImmSetCompositionWindow should be called, of course.
> 
> > Sorry I'm asking all these questions, but I don't know enough about
> > IME programming, and need to understand this in order to see that the
> > patch doesn't break anything else.
> 
> Current Emacs's IME implementation has this bug.
> It's almost imposible to input desired text because of the invisible
> composition window.
> This patch is nice improvement.

Thanks, I installed your change in the development sources, as commit
37e3549, and I'm marking this bug "done".





  parent reply	other threads:[~2015-02-19 11:44 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18  5:20 bug#11732: 24.1; Microsoft IME Japanese input problem xavier.dahan
2015-02-17 10:26 ` Fujii Hironori
2015-02-18 15:17   ` Eli Zaretskii
2015-02-19  2:03     ` Fujii Hironori
2015-02-19  6:44       ` Eli Zaretskii
     [not found]         ` <CALus1PmqiC8TnQTfcpVFD5ObjqbK_4hkOczRKmG1=+mkWXUHWQ@mail.gmail.com>
2015-02-19 11:44           ` Eli Zaretskii [this message]
2015-03-06 20:29             ` Eli Zaretskii
2015-03-06 22:37               ` Fujii Hironori
2015-03-07 10:53                 ` Eli Zaretskii
2015-03-09  2:13               ` Fujii Hironori
2015-03-09 16:30                 ` Eli Zaretskii
2018-06-26  9:10 ` bug#11732: Follow-up to bug#11732 Masayuki Hatta
2018-06-27 15:54   ` Eli Zaretskii
2018-06-28  8:04     ` martin rudalics
2018-06-28 10:13       ` Masayuki Hatta
2018-06-28 12:25         ` martin rudalics
2018-06-28 13:09           ` Eli Zaretskii
2018-06-28 10:11     ` Masayuki Hatta
2018-06-28 13:28       ` Eli Zaretskii
2018-06-28 19:17         ` Noam Postavsky
2018-06-28 19:24           ` Eli Zaretskii
2018-06-29  7:39             ` Masayuki Hatta
2018-06-29  8:43               ` martin rudalics
2018-06-29  8:59                 ` Eli Zaretskii
2018-06-30  3:14                 ` Masayuki Hatta
2018-06-30  7:46                   ` Eli Zaretskii
2018-06-30  8:30                     ` Masayuki Hatta
2018-06-29  8:56               ` Eli Zaretskii
2018-06-29  8:43     ` martin rudalics
2018-06-29  9:07       ` Eli Zaretskii
2018-06-30  8:06         ` martin rudalics
2018-06-30 11:32           ` Eli Zaretskii
2018-06-30 12:51             ` martin rudalics
2018-06-30 13:21               ` Eli Zaretskii
2018-07-01  9:00                 ` martin rudalics
2018-07-01 14:29                   ` Eli Zaretskii
2018-07-03  8:29                     ` martin rudalics
2018-07-03 18:50                       ` Eli Zaretskii
2018-07-07  7:45                         ` Tak Kunihiro
2018-07-07 10:00                           ` Eli Zaretskii
2018-07-07 10:21                             ` martin rudalics
2018-07-07 11:32                               ` Eli Zaretskii
2018-07-01 14:34             ` 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=8361ay3z36.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11732-done@debbugs.gnu.org \
    --cc=fujii.hironori@gmail.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.
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).