On Mon, 24 Nov 2008 16:53:20 +0300, Christopher Wright
<[EMAIL PROTECTED]> wrote:
John C wrote:
novice2 Wrote:
i am afraid that windows API named *W works with UCS2 string.
but D wchar[] is UTF-16.
Wrong - Windows has used UTF-16 as native since Windows 2000.
Actually, you're both right. UCS2 is UTF-16.
No. A quote from Wikipedia:
"Because of the technical similarities and upwards compatibility from
UCS-2 to UTF-16, the two encodings are often erroneously conflated and
used as if interchangeable, so that strings encoded in UTF-16 are
sometimes misidentified as being encoded in UCS-2."
"UTF-16 is the native internal representation of text in the Microsoft
Windows 2000/XP/2003/Vista/CE; Qualcomm BREW operating systems; the Java
and .NET bytecode environments; Mac OS X's Cocoa and Core Foundation
frameworks; and the Qt cross-platform graphical widget toolkit."
"Older Windows NT systems (prior to Windows 2000) only support UCS-2."
