<?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 on: Big5 to UTF-8 on Chinese Windows</title>
	<atom:link href="http://randomstringofwords.com/big5-to-utf-8-on-chinese-windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://randomstringofwords.com/big5-to-utf-8-on-chinese-windows/</link>
	<description>RandomStringOfWords.com &#124;&#124; RSoW.com</description>
	<lastBuildDate>Wed, 01 Feb 2012 01:03:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Shawn</title>
		<link>http://randomstringofwords.com/big5-to-utf-8-on-chinese-windows/comment-page-1/#comment-325</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Thu, 10 May 2007 02:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://info.rsow.com/big5-to-utf-8-on-chinese-windows/#comment-325</guid>
		<description>The problem basically lies in SQL Server only supporting UCS-2, and not UTF-8. Among Microsoft&#039;s suggestions for storing UTF-8 in SQL Server: use binary (ie. non-searchable, non-usable) fields to store all of your strings, or convert your entire application to our way instead of UTF-8. As far as I know, this stays this way until the next version of SQL Server, due for release sometime in the future (2008, I think). Unless of course, they drop that feature or delay the product.

The real solution: don&#039;t use SQL Server if you need to store UTF-8 bytes.

It does amuse me that Microsoft&#039;s site sends Content-Type: text/html; charset=utf-8, since I have no clue what a browser would do if it sent Content-Type: text/html; charset=ucs-2. But, then, since they use IIS, ASP, and Windows as their server, they have the only platform supported for automatic conversion to UTF-8 for output when using SQL Server.

Also see: &quot;What is the difference between UCS-2 and UTF-16?&quot; http://unicode.org/faq/basic_q.html#25</description>
		<content:encoded><![CDATA[<p>The problem basically lies in SQL Server only supporting UCS-2, and not UTF-8. Among Microsoft&#8217;s suggestions for storing UTF-8 in SQL Server: use binary (ie. non-searchable, non-usable) fields to store all of your strings, or convert your entire application to our way instead of UTF-8. As far as I know, this stays this way until the next version of SQL Server, due for release sometime in the future (2008, I think). Unless of course, they drop that feature or delay the product.</p>
<p>The real solution: don&#8217;t use SQL Server if you need to store UTF-8 bytes.</p>
<p>It does amuse me that Microsoft&#8217;s site sends Content-Type: text/html; charset=utf-8, since I have no clue what a browser would do if it sent Content-Type: text/html; charset=ucs-2. But, then, since they use IIS, ASP, and Windows as their server, they have the only platform supported for automatic conversion to UTF-8 for output when using SQL Server.</p>
<p>Also see: &#8220;What is the difference between UCS-2 and UTF-16?&#8221; <a href="http://unicode.org/faq/basic_q.html#25" rel="nofollow">http://unicode.org/faq/basic_q.html#25</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://randomstringofwords.com/big5-to-utf-8-on-chinese-windows/comment-page-1/#comment-324</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 09 May 2007 14:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://info.rsow.com/big5-to-utf-8-on-chinese-windows/#comment-324</guid>
		<description>Shawn could you sum up what the problem/solution was to this?</description>
		<content:encoded><![CDATA[<p>Shawn could you sum up what the problem/solution was to this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://randomstringofwords.com/big5-to-utf-8-on-chinese-windows/comment-page-1/#comment-323</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Wed, 02 May 2007 03:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://info.rsow.com/big5-to-utf-8-on-chinese-windows/#comment-323</guid>
		<description>I actually meant how SQL Server doesn&#039;t actually support UTF-8...at all (http://support.microsoft.com/kb/232580). Not to mention how your queries have to have the SQL in ASCII, with the data in UCS-2.

Yeah, it would kinda shock me if it didn&#039;t run DB2, but you never know...</description>
		<content:encoded><![CDATA[<p>I actually meant how SQL Server doesn&#8217;t actually support UTF-8&#8230;at all (<a href="http://support.microsoft.com/kb/232580" rel="nofollow">http://support.microsoft.com/kb/232580</a>). Not to mention how your queries have to have the SQL in ASCII, with the data in UCS-2.</p>
<p>Yeah, it would kinda shock me if it didn&#8217;t run DB2, but you never know&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://randomstringofwords.com/big5-to-utf-8-on-chinese-windows/comment-page-1/#comment-322</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 02 May 2007 00:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://info.rsow.com/big5-to-utf-8-on-chinese-windows/#comment-322</guid>
		<description>Well the DB in question is DB2.. I assumed the bug tracking tools db was also DB2.. would be a little surprised if it wasn&#039;t.. but.. that&#039;d be funny..</description>
		<content:encoded><![CDATA[<p>Well the DB in question is DB2.. I assumed the bug tracking tools db was also DB2.. would be a little surprised if it wasn&#8217;t.. but.. that&#8217;d be funny..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://randomstringofwords.com/big5-to-utf-8-on-chinese-windows/comment-page-1/#comment-321</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Tue, 01 May 2007 23:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://info.rsow.com/big5-to-utf-8-on-chinese-windows/#comment-321</guid>
		<description>*cough* SQL Server *cough*

That bug-tracking train wreck has temped me to find security holes in various places just so I could see if tracking a XSS or SQL injection bug would break it. :-)</description>
		<content:encoded><![CDATA[<p>*cough* SQL Server *cough*</p>
<p>That bug-tracking train wreck has temped me to find security holes in various places just so I could see if tracking a XSS or SQL injection bug would break it. <img src='http://randomstringofwords.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

