At 11:15 AM 4/27/00 -0700, you (Alexandre Julliard) wrote:
>The long term solution is clearly 2 (Windows Unicode format
>internally). It's the only viable solution to remain reasonably
>compatible with Windows dlls.
>
Another interesting point is that the app and the system can share
memory.
Consider the following situation : a programs reads in an ascii file, translates
the buffer to Unicode with MultiByteToWideChar, then gives the buffer
to the system (that's what is doing Notepad NT, with the EM_SETHANDLE
message for the edit control); if the internal format (in this case the format used in
the
edit control buffer) is not the same as the one expected by the app, it will not work
(actually, that's what is happening now, since the internal format of the edit control
is ascii :-))
Of course MultiByteToWideChar could translate to the internal Wine format, but
it can be wrong since the app has still full access to the buffer and is able to work
*directly*
on it, relying on its own knowledge on what the internal format is supposed to be.
Also, apps
may call MultiByteToWideChar to exchange data with other systems...
Gerard
