Tim Roberts wrote:
> Roger Upole wrote:
>> Just supplying the Dll is not sufficient. The .pyd would also have to be
>> linked against unicows.lib, which would mean creating a separate release
>> for
>> win98.
>>
>
> Not so, actually. Microsoft was quite clever with this. Unicows.lib
> checks on
Roger Upole wrote:
> Just supplying the Dll is not sufficient. The .pyd would also have to be
> linked against unicows.lib, which would mean creating a separate release for
> win98.
>
Not so, actually. Microsoft was quite clever with this. Unicows.lib
checks on its first invocation to see i
Tim Roberts wrote:
> Roger Upole wrote:
>> Mark suggested that I get some feedback from the community regarding
>> some of the issues involved in creating a Unicode build of win32api.
>>
>> Some functions already allow you to call the ansi or wide-character
>> version,
>> such as FormatMessage/For
Roger Upole wrote:
> Mark suggested that I get some feedback from the community regarding
> some of the issues involved in creating a Unicode build of win32api.
>
> Some functions already allow you to call the ansi or wide-character version,
> such as FormatMessage/FormatMessageW. This leaves some
Mark suggested that I get some feedback from the community regarding
some of the issues involved in creating a Unicode build of win32api.
Some functions already allow you to call the ansi or wide-character version,
such as FormatMessage/FormatMessageW. This leaves some ambiguity
as to how they sh
