<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Windows on UberMongoose</title>
		<link>http://localhost:1313/tags/windows/</link>
		<description>Recent content in Windows on UberMongoose</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 06 Nov 2012 13:46:55 +0530</lastBuildDate>
		
			<atom:link href="http://localhost:1313/tags/windows/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Unicode and Windows</title>
				<link>http://localhost:1313/post/unicode-and-windows/</link>
				<pubDate>Tue, 06 Nov 2012 13:46:55 +0530</pubDate>
				<guid>http://localhost:1313/post/unicode-and-windows/</guid>
				<description>&lt;p&gt;Unicode string support in Windows is a strange beast.&lt;/p&gt;&#xA;&lt;p&gt;When Microsoft hired Dave Cutler and others to write a new OS for them they were thinking about writing a new version of OS/2. In fact the new Microsoft OS was a combined effort by Microsoft and IBM that would have resulted in OS/2 version 3.0 if not for the success of Microsoft’s own Windows 3 which made them reconsider that approach. At the eleventh hour they shifted their API from the extended OS/2 API that was to be the way things got done on the new OS to an extended version of the Windows API. This last minute change was possible due to some clever trickery on the part of the programmers who wrote the new Windows OS but it resulted in a strange API, especially when it came to string handling in the new OS known to history as Windows NT 3.1.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
