I remember figuring this out a while ago, but I forgot since then...
under what conditions does WM_IME_CHAR return ascii question marks and not
the actual Unicode character. Does it have to do with _UNICODE not being
defined in the application?
And, which system is deciding to send the question mark? Is it the IME
itself, or some layer between my app and the IME?
Sounds like maybe you are expecting to see chars in the IDE even if they are
MBCS off the current default code page?
--
MichKa
Michael Kaplan
Trigeminal Software, Inc. -- http://www.trigeminal.com/
International VB? -- http://www.i18nWithVB.com/
C++? MSLU -- http://msdn.microsoft.com/msdnmag/issues/01/10/
"David Herman" <dhe...@soe.sony.com> wrote in message
news:O8q838A4BHA.2684@tkmsftngp07...
Keith
"Michael (michka) Kaplan" <forme...@nospam.trigeminal.spamless.com> wrote
in message news:OPnuM$A4BHA.1364@tkmsftngp05...
--
MichKa
Michael Kaplan
Trigeminal Software, Inc. -- http://www.trigeminal.com/
International VB? -- http://www.i18nWithVB.com/
C++? MSLU -- http://msdn.microsoft.com/msdnmag/issues/01/10/
"Keith Patella" <ke...@stainlesssteelstudios.com> wrote in message
news:O4iO$ch4BHA.1812@tkmsftngp02...
"Michael (michka) Kaplan" <forme...@nospam.trigeminal.spamless.com> wrote
in message news:#cctURk4BHA.1920@tkmsftngp05...
--
MichKa
Michael Kaplan
Trigeminal Software, Inc. -- http://www.trigeminal.com/
International VB? -- http://www.i18nWithVB.com/
C++? MSLU -- http://msdn.microsoft.com/msdnmag/issues/01/10/
"Keith Patella" <ke...@stainlesssteelstudios.com> wrote in message
news:uqrB6tl4BHA.1924@tkmsftngp05...
I actually get the ASCII value for a question mark out of the IME through
WM_IME_CHAR.
For now, I'm avoiding the problem by getting my character from
ImmGetCompositionStringW.
Thanks, all!
Dherman
--
MichKa
Michael Kaplan
Trigeminal Software, Inc. -- http://www.trigeminal.com/
International VB? -- http://www.i18nWithVB.com/
C++? MSLU -- http://msdn.microsoft.com/msdnmag/issues/01/10/
"David Herman" <dhe...@soe.sony.com> wrote in message
news:u2XfrXw5BHA.1628@tkmsftngp02...
Hey MichKa!
I basically didn't set up too much. I am working on code that is 3 or 4
years old and was not designed with localization in mind. The first change I
made was to add a WM_IME_CHAR section to our application's WndProc, and I
breakpointed the code. (I don't know if this matters, but I was not able to
define either UNICODE or _UNICODE because this broke things terribly)
Then, I ran the application in a window, pressed Alt-Shift to manually
bring up different IMEs and started typing away. When Windows had closed off
the composition window, my breakpoint got called with the ASCII question
mark (wParam is 63).
So, your guess is as good as mine =) I'm sure there's some setting
somewhere that's off.
Dherman
This is by design and you should start handling the
WM_INPUTLANGCHANGEREQUEST message to refuse changes to these other input
locales.
And you should think about making a Unicode product, in the future... :-)
--
MichKa
Michael Kaplan
Trigeminal Software, Inc. -- http://www.trigeminal.com/
International VB? -- http://www.i18nWithVB.com/
C++? MSLU -- http://msdn.microsoft.com/msdnmag/issues/01/10/
"David Herman" <dhe...@soe.sony.com> wrote in message
news:evFRocx5BHA.2264@tkmsftngp07...