<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for flatware-engine.org</title>
	<atom:link href="http://flatware-engine.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://flatware-engine.org</link>
	<description>An Open Source 2D Game Engine</description>
	<lastBuildDate>Wed, 29 Sep 2010 14:33:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>Comment on Unicode is a PAIN! by madcat13</title>
		<link>http://flatware-engine.org/2010/09/17/unicode-is-a-pain/comment-page-1/#comment-5</link>
		<dc:creator>madcat13</dc:creator>
		<pubDate>Wed, 29 Sep 2010 14:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://flatware-engine.org/?p=148#comment-5</guid>
		<description>Ok, we&#039;ve got Unicode figured out now, although we&#039;ve had to go back and make a few changes to accommodate handling it.
Right now, we are storing all strings internally as Unicode. We have also made some conversion utility methods which will convert back and forth between UTF8 and Unicode strings, as all text input and output will be through UTF8 multibyte characters.  This will force us to write three pass-through methods for each string handling method in order to keep the interface clean (to handle standard C++ strings, C-style strings and wide character arrays).
This makes things a little uglier behind the scenes than we wanted, but hopefully things will still be fairly transparent to the user.
I&#039;ve been pretty busy with other things life keeps throwing at me, so I haven&#039;t been able to code as much as I had hoped, but I&#039;m still plugging away as much as possible.

Look for more updates as events warrant :D

MadCat13</description>
		<content:encoded><![CDATA[<p>Ok, we&#8217;ve got Unicode figured out now, although we&#8217;ve had to go back and make a few changes to accommodate handling it.<br />
Right now, we are storing all strings internally as Unicode. We have also made some conversion utility methods which will convert back and forth between UTF8 and Unicode strings, as all text input and output will be through UTF8 multibyte characters.  This will force us to write three pass-through methods for each string handling method in order to keep the interface clean (to handle standard C++ strings, C-style strings and wide character arrays).<br />
This makes things a little uglier behind the scenes than we wanted, but hopefully things will still be fairly transparent to the user.<br />
I&#8217;ve been pretty busy with other things life keeps throwing at me, so I haven&#8217;t been able to code as much as I had hoped, but I&#8217;m still plugging away as much as possible.</p>
<p>Look for more updates as events warrant <img src='http://flatware-engine.org/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>MadCat13</p>
]]></content:encoded>
	</item>
</channel>
</rss>

