Re: Win32 Needs

Right, but the question becomes: How to provide it, and /not/ cut off
Win 9x for our customer's customers.

Use Unicode internally all the time (just make sure every DevCo developer knows not to confuse UTF16 with UCS2, if in doubt, better take no risk and pick UTF8 or UTF32).
Then at the very last moment, when you're going to talk to the WinAPI, fallback to Ansi when Unicode isn't supported. Yes, that'll slow ANSI execution a bit, but better slowed a bit than not running at all ^_^

There are relatively few APIs where you have to pass or retrieve strings, and if the VCL is upgraded to handle it, you could end up with something much simpler and cleaner than what TntUnicode controls have to do (they have to do a lot of working around).

Eric
.