<?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>What is wrong with that web page?</title><link>http://blogs.msdn.com/michkap/archive/2005/10/28/486034.aspx</link><description>The other day, my manager's manager's manager Delan was looking at various web sites and on one of them there was an unusual display issue on several pages. Basically, each of the pages in question had text on them that looked like this: "?/font&amp;gt;"</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: What is wrong with that web page?</title><link>http://blogs.msdn.com/michkap/archive/2005/10/28/486034.aspx#486129</link><pubDate>Fri, 28 Oct 2005 12:39:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:486129</guid><dc:creator>CornedBee</dc:creator><description>Lesson learned: validate!&lt;br&gt;Because the W3C validator catches missing encoding declarations (which are misnamed charset declarations).</description></item><item><title>re: What is wrong with that web page?</title><link>http://blogs.msdn.com/michkap/archive/2005/10/28/486034.aspx#486145</link><pubDate>Fri, 28 Oct 2005 14:06:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:486145</guid><dc:creator>Will</dc:creator><description>Of course, I feel bound to make some criticism of a layout which has list bullets wrapped in font tags.&lt;br&gt;&lt;br&gt;&amp;lt;UL&amp;gt; is hardly a difficult concept.&lt;br&gt;&lt;br&gt;</description></item><item><title>re: What is wrong with that web page?</title><link>http://blogs.msdn.com/michkap/archive/2005/10/28/486034.aspx#486153</link><pubDate>Fri, 28 Oct 2005 14:43:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:486153</guid><dc:creator>Ben Bryant</dc:creator><description>I always love your blog, but I found this confusing: &amp;quot;U+2022 U+003c (•&amp;lt;) which for me was being read as 0x95 0x3c was for her being converted to &amp;quot;?&amp;quot; &amp;quot; Once I realized that the U+2022 is 0x95 in Windows-1252 then it was clear that for *both* of you the bytes you were seeing were 0x95 0x3c. So you were both trying to interpret 0x95 0x3c in your respective double byte encodings (e.g. 0x95 is a lead byte and 0x3c is not a valid trail byte in either, therefore the question mark).&lt;br&gt;To say that you have U+2022 U+003c in the page is incorrect since it is really a matter of guessing. It is also misleading to use the Unicode way of expressing those characters because no Unicode encoding is involved AT ALL until the browser's internal representation of the page. Those are the intended characters, yes, but I'm just trying to explain why I found your explanation confusing.</description></item><item><title>Just use &amp;bull;</title><link>http://blogs.msdn.com/michkap/archive/2005/10/28/486034.aspx#486331</link><pubDate>Fri, 28 Oct 2005 21:20:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:486331</guid><dc:creator>Maurits</dc:creator><description>&lt;a rel="nofollow" target="_new" href="http://www.w3.org/TR/REC-html40/sgml/entities.html"&gt;http://www.w3.org/TR/REC-html40/sgml/entities.html&lt;/a&gt;&lt;br&gt;&amp;lt;!ENTITY bull     CDATA &amp;quot;&amp;amp;#8226;&amp;quot; -- bullet = black small circle,&lt;br&gt;                                     U+2022 ISOpub  --&amp;gt;&lt;br&gt;</description></item><item><title>Microsoft Internet Explorer DBCS Remote Memory Corruption Vulnerability</title><link>http://blogs.msdn.com/michkap/archive/2005/10/28/486034.aspx#574722</link><pubDate>Wed, 12 Apr 2006 10:11:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:574722</guid><dc:creator>傻傻Horace</dc:creator><description>Microsoft Internet Explorer DBCS Remote Memory Corruption Vulnerability&lt;br&gt;</description></item></channel></rss>