🚀 go-pugleaf

Thank you Alan

but how to support unicode for win9x in my BCB 6.0 program

MS only offer a lib file with coff format, no omf format.

and I can't convert it to omf format by coff2omf.exe

further hint?

sky


"Alan Bellingham" <alanb@episys.com> 
??????:aonjn152reu5to2st6ptftml5gomh74ojd@4ax.com...
> "sky" <akeehuang@163.com> wrote:
>
>>The program need run under Win9X/Win2000/WinXP
>>
>>I want to draw some Unicode text on the standard window DC by API 
>>function.
>
> One of the major differences between the semi-16 and full-32-bit
> versions of Windows is that Win95/98/Me were not designed to support
> Unicode, whereas Windows NT/2000/XP are.
>
> (Some history - back in 1992-94, Microsoft were hot on the NT line of
>  OSes. But they knew they couldn't get everyone using Windows 3.1 to
>  transition to Windows NT at once, so they produced Chicago - aka
>  Windows 95. It was a kludge of Windows 3.1 code, Windows NT code, and
>  some new stuff from neither. It existed to allow people to use those
>  fragile insecure 16-bit Windows apps, and was only supposed to have
>  one version, while they produced a newer better NT 4, and got everyone
>  across to that.
>
>  But of course, people wouldn't go for NT. It wasn't pretty enough. And
>  there came the 98 and Me patches, before Microsoft finally knocked the
>  whole mishmash on the head and dispatched it to the sky. But oh no,
>  the zombie will not die!)
>
> If you really do have to support Unicode on 9x, then the following link
> is probably the best place to find out the info:
>
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mslu/winprog/microsoft_layer_for_unicode_on_windows_95_98_me_systems.asp
>
> However, I'd suggest implementing for 2000 and later, and only consider
> the "Unicode Layer" described there if you really have to.
>
> Alan Bellingham
> -- 
> ACCU Conference 2006 - 19-22 April, Randolph Hotel, Oxford, UK