How can I use ToUnicode without breaking dead key support?

Question

A similar question has already been asked, so I'm not going to waste time trying to explain it again, the existing discussion can be found here: ToAscii / ToUnicode in the keyboard hook destroys dead keys

The reason I am posting a new question, however, is because I seem to have come across a “solution”, but I'm not quite sure how to implement it.

This blog post seems to offer a solution to the ToUnicode problem killing dead key support: http://www.siao2.com/2005/01/19/355870.aspx

However, I am not sure how to implement the proposed solution. A push in the right direction would be very helpful.

To be clear, the part I'm talking about is this:

There are two ways around this:

1) You can continue to call ToUnicode with the same information until it is cleared, and then call it again to return the state to where it was if you didn’t type anything, or

2) You can download all the keyboard information in advance, and then when they print the information, you can find in your own information cache what the keys mean without having to call the API later.

I'm not quite sure how to do any of these things (the keyboard and internationalization are far from my forte), so any help would be greatly appreciated.

thank

Answer 1

. . ToUnicode() , . . , .

Microsoft lookDontTouch wFlags; API.

Answer 2

, , . , , ToUnicode, . , DLL.

, , 64- Windows.