[1/3] user32: Convert data in WM_DDE_EXECUTE to unicode when expected.

[Vincent Povirk]

For bug 13891.

We have tests that show that ddeml generally ensures the text of a dde execute command is in the format expected by the server before sending the XTYP_EXECUTE notification, disregarding the text format the client claims to be using UNLESS both the client and the server are unicode.

When a ddeml client sends WM_DDE_EXECUTE, it generally only converts the text if the client is unicode but the server (and therefore the conversation) is not. We have tests that verify this behavior, and MSDN's documentation for WM_DDE_EXECUTE also appears to agree.

Therefore, the conversion must happen on the server side.

This generally ensures that a ddeml server will get unicode data, which makes it possible to correctly fix winebrowser.

The third patch in this series is not needed to fix winebrowser, but it makes the tests pass in the case where an ansi client sends unicode data to an ansi ddeml server.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20100513/6a27b38e/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0001-user32-Convert-data-in-WM_DDE_EXECUTE-to-unicode-when-.txt
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20100513/6a27b38e/attachment.txt>