Re: TCHAR string?


"Jonathan Wood" <jwood@xxxxxxxxxxxxxxxx> wrote in message
news:OvdQXlOFGHA.740@xxxxxxxxxxxxxxxxxxxxxxx
> Pete,
>
>>> Except of course, that not all versions of Windows support Unicode.
>>
>> Technically that is indeed true, however even lowely Windows 95 supports
>> a subset of the Win32 API in Unicode for things like COM support etc. In
>> addition, Microsoft delivered the Microsoft Layer for Unicode on Windows
>> 95/98/Me to add to this support.
>> http://www.microsoft.com/globaldev/handson/dev/mslu_announce.mspx
>
> Yes, but even the Microsoft Layer for Unicode has limitations. I'm not
> saying it isn't useful. But I didn't think it was worth doing such a
> version with my latest Unicode application.

I suppose that it really all depends upon what it is you are doing...
However, it occurs to me that at this late point in the lifecycle of the
operating systems that support the MSLU it likely wouldn't be worth
targeting a version for them anyway!

>
>> Realistically, all of the modern operating systems from Microsoft,
>> including Windows CE, now support Unicode.
>
> I disagree with this statement. Yes, there is some support there. But if
> you have a significant application that was built to use Unicode, you'd
> have an enormous job on your hand getting it to work on Win95, and it will
> require the distribution of extra code in the form of a DLL.

Perhaps I should have clarified my statement. When I refer to "modern
operating systems", I mean those that have the Windows NT kernel. This
disqualifies 95/98 & ME and earlier versions of Windows.

I understand your point, however, but I think that if for some strange
reason you looked at back porting an application to Windows 9.X, Unicode
support would likely be the *least* of your problems!

-Pete


.

Relevant Pages

  • Re: unicode apps?
    ... With Unicode or UTF-8 that problem is ... In my way of saying things: in Windows you don't load a character code ... The code page support is installed or not. ... change the system code page to mach the document code page ...
    (microsoft.public.vc.mfc)
  • Re: Why does ActiveSync still NOT support UNICODE?!
    ... ActiveSync in version 2 did support UNICODE. ... Then came the "unified" build of ActiveSync version 3, ... and Windows 9x. ...
    (microsoft.public.pocketpc.activesync)
  • Re: how to copy/paste international strings to the VS editor?
    ... If you click on the menu File - Save As, it lets you choose whether to save the file as ANSI or Unicode. ... Of course there's no such thing as Japanese encoding ASCII. ... It sounds like you're using a foreign version of Windows without Asian language support. ... At the same time, if you're using Windows XP, you'll need to find and enable an option that says to extend text support to all applications. ...
    (microsoft.public.vc.mfc)
  • Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
    ... but the Help for GetProcAddress mentions the Microsoft Layer for ... Unicode issue, and the Help for Microsoft Layer for Unicode lists ... Requires Windows XP, Windows 2000 Professional, Windows NT ...
    (microsoft.public.vb.winapi)
  • Re: Microsoft Layer for Unicode on Windows 95/98/Me systems
    ... but the Help for GetProcAddress mentions the Microsoft Layer ... Unicode issue, and the Help for Microsoft Layer for Unicode lists ... Requires Windows XP, Windows 2000 Professional, Windows NT ...
    (microsoft.public.vb.winapi)
Loading