News for hackers. Stuff that matters.
Re:UTF-8 good, UTF-16 bad by getsat on Tuesday February 08, 2011 @10:19AM (#2193101)
The Windows NT development team made the decision to standardise on UTF-16. Every release of Windows since the original NT uses UTF-16 internally for all its "wide character" API calls (e.g., wcslen() and FindWindowW()).
Re:UTF-8 good, UTF-16 bad by sedachv on Tuesday February 08, 2011 @11:02PM (#2196234)
Windows has only had UTF-16 interfaces since 2000, NT was based around UCS-2.
Re:UTF-8 good, UTF-16 bad by getsat on Thursday February 10, 2011 @04:12PM (#2203748)
Hmm. I recall the SysInternals books saying it was NT4, not 5. I could be mistaken, though.