<?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>Why there is no charset property in ASPX pages</title><link>http://blogs.msdn.com/mikhailarkhipov/archive/2004/08/07/210769.aspx</link><description>...or how HTML editor handles file encoding. First, Visual Studio is a Unicode application and actually even supports Unicode Surrogates Pairs . Most of Web pages, however, are not stored in Unicode. Therefore when opening a Web page VS has to figure</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Why there is no charset property in ASPX pages</title><link>http://blogs.msdn.com/mikhailarkhipov/archive/2004/08/07/210769.aspx#524005</link><pubDate>Fri, 03 Feb 2006 15:42:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:524005</guid><dc:creator>Dimitris</dc:creator><description>Mister, You are God! &lt;br/&gt;Thank you thank you thank you so very much for this article. &lt;br/&gt;I am using Visual Web Developer 2005. All my aspx pages contain Greek characters. I had tried everything: meta tag, globalization in web.config. No result. I then saw the f*** &amp;quot;auto-detect utf-8 encoding without signature&amp;quot; and got suspicious about vs doing black magic behind my back. But then still again, shit and hell. I then read your post and figured out what really goes on with file encodings and vs.&lt;br/&gt;&lt;br/&gt;cheers&lt;br/&gt;dimitris</description></item></channel></rss>