minwin unicode

[Walter Bright]

Chris Miller wrote:
> I meant to say 98 and ME, and I agree that how std.file does it is 
> better, it's how I usually do it, e.g. in DFL. However, if a library has 
> less interest in supporting win9x/ME, and more interest in simplifying 
> unicode, it may be easier to just use MSLU, even though I personally 
> probably still wouldn't, but it's still an option.

It's an option, but a poor one. MSLU doesn't actually add unicode 
support. It just provides translations just like std.file does. And 
worse, it requires you to ship the MSLU dll with your product, which 
makes it a nuisance for customers.