minwin unicode
Bill Baxter
wbaxter at gmail.com
Sat Dec 2 13:22:20 PST 2006
Tomas Lindquist Olsen wrote:
> Tomas Lindquist Olsen wrote:
>
>
>>I've been looking at unicode support for MinWin in Windows.
>>
>>From minwin/todo:
>>* mswindows
>> - A vs W for string inputs - convert to wchar
>>
>>It seems that sticking with char[] and only doing the toUTF16z
>>conversions under the hood is the most feasible.
>>
>>I have attached a patch (made with tortoiseSVN) that makes
>>minwin/button.d work with unicode. It adds a few W functions to
>>minwin/mswindows.d as well.
>>
>>Is there a better way?
>>Feedback is much appreciated, I think MinWin should support unicode
>>properly, and it's not that much work with this approach.
>>
>>Does unicode work with GTK/Motif?
>>
>>-- Tomas
>
>
> Not sure whether the MinWin forum or this newsgroup is the right place
> for the discussion, but I'm looking for feedback on this:
>
> http://www.dsource.org/forums/viewtopic.php?t=2096
>
> -- Tomas
>
Do you care about Win95? If so then I recall there are some limitations
to using unicode there, and you need something called unicows.dll to
make it work at all. I think unicows only supports a subset of the
win32 api.
Personally I don't care about Win95, but apparently a lot of people
still do.
If you don't care about Win95, then I believe you're right that the -W
functions are the way to go.
[btw I'm not a big fan of forums... but I also realize it doesn't make
sense to have dozens of project-specific threads going on here --
especially when 'here' is the "announce" newsgroup ;-) Can DSource host
mailing lists? Could Walter host project-specific newsgroups?]
--bb
More information about the Digitalmars-d-announce
mailing list