http://bugs.winehq.org/show_bug.cgi?id=13891
--- Comment #53 from Vincent Povirk madewokherd@gmail.com 2010-05-13 14:50:28 --- Created an attachment (id=27939) --> (http://bugs.winehq.org/attachment.cgi?id=27939) user32: Change the conversion logic in WDML_BuildExecuteCommand (fixes some tests but breaks others)
This patch fixes string conversion in the cases where both the client and server are using dddml. However, it breaks it in the case where only the client uses ddeml and the server uses window messages directly.
The MSDN documentation for WM_DDE_EXECUTE explains why we test whether both the client and server window are unicode, since this determines whether the server expects a unicode string.
This suggests to me that ddeml on the server side needs to determine the appropriate type of encoding for the data when it gets a WM_DDE_EXECUTE message and convert it to what the server expects, rather than on the client side as my patch does.