<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>There is no such thing as a surrogate character (dammit!)</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx</link><description>The title of this post, including the parenthetical note, is something that people associated with the Unicode Standard have to tell people all the time (of course generally people only say that parenthetical note to themselves, and really only because</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: There is no such thing as a surrogate character (dammit!)</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx#444824</link><pubDate>Fri, 29 Jul 2005 10:43:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:444824</guid><dc:creator>Michael</dc:creator><description>The evil like Char.IsSurrogate comes from the fact that Char managed type, as well as wchar_t (under Windows) really represent just two bytes in Utf16 encoding, not the Unicode character. I always mentally translate it, and then Utf16CodePoint.IsSurrogate does makes sense :)</description></item><item><title>re: There is no such thing as a surrogate character (dammit!)</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx#444940</link><pubDate>Fri, 29 Jul 2005 18:13:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:444940</guid><dc:creator>Michael S. Kaplan</dc:creator><description>Well, that is the slightly more benign use (IMHO) -- both types are defined for MS platforms as using UTF-16, an it is just asking if the thing in the Char or WCHAR is a surrogate....</description></item><item><title>re: There is no such thing as a surrogate character (dammit!)</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx#444948</link><pubDate>Fri, 29 Jul 2005 18:37:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:444948</guid><dc:creator>Ben Bryant</dc:creator><description>Well put. I'll try to always keep this in mind. But looking at XmlWriter WriteSurrogateCharEntity it seems to be named to be consistent with WriteCharEntity which I think is actually incorrect in the first place -- it is a &amp;quot;Numeric Character Reference&amp;quot;, not an &amp;quot;Entity Reference&amp;quot; and certainly leaving off the term &amp;quot;Reference&amp;quot; or at least &amp;quot;Ref&amp;quot; is bad usage; it should be WriteCharRef and WriteSupplementaryCharRef for use with UTF-16. They also have WriteEntityRef which is actually an &amp;quot;Entity Reference,&amp;quot; so they apparently thought leaving the &amp;quot;Ref&amp;quot; part off would make it a Numeric Character Reference! This whole API shows a real confusion in terms, in particular a craziness around the term &amp;quot;Entity.&amp;quot; Dare Obasanjo oversaw this right? He should explain it. But coming back to your point, the Char in the method name may be intending to refer to the output (which is actually a supplementary character) and not the surrogate pair that is input judging from the correlation with WriteCharEntity.&lt;br&gt;</description></item><item><title>Why my syndication links were broken....</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx#445840</link><pubDate>Mon, 01 Aug 2005 03:47:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:445840</guid><dc:creator>Sorting It All Out</dc:creator><description>The other day I complained about how My syndication links are broken.&lt;br&gt;We can blame it all on surrogates!...</description></item><item><title>Maybe there is such a thing as a surrogateS character (dammit!)</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx#525725</link><pubDate>Mon, 06 Feb 2006 18:25:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:525725</guid><dc:creator>Sorting It All Out</dc:creator><description>(No, the title of this post does not contain a typo!)&lt;br&gt;I have a regular reader of this blog who is a...</description></item><item><title>If it ain't UTF-16 then it ain't having no surrogate pairs, baby!</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx#5263374</link><pubDate>Wed, 03 Oct 2007 17:32:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5263374</guid><dc:creator>Sorting It All Out</dc:creator><description>&lt;p&gt;The other day, Ramanathan asked: Hi, I have the following surrogate character 𠄃 that can be encoded&lt;/p&gt;
</description></item><item><title>If you would wait till I *FINISHED* what I was trying to say, you punk... (aka Premature validation)</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx#5624431</link><pubDate>Tue, 23 Oct 2007 17:17:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5624431</guid><dc:creator>Sorting It All Out</dc:creator><description>&lt;p&gt;This may have happened to you before. Sometimes I am trying to have a conversation with someone. And&lt;/p&gt;
</description></item><item><title>I'm simply saying that life^H^H^H^Hcharacters, uh... find a way</title><link>http://blogs.msdn.com/michkap/archive/2005/07/27/444101.aspx#6141756</link><pubDate>Mon, 12 Nov 2007 18:13:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6141756</guid><dc:creator>Sorting It All Out</dc:creator><description>&lt;p&gt;Regular reader Jan Kučera asked in response to If you would wait till I *FINISHED* what I was trying&lt;/p&gt;
</description></item></channel></rss>