<?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: Expression Web - What? A Bug Already?</title>
	<atom:link href="http://blog.pinkandyellow.com/microsoft-expression/expression-web-what-a-bug-already-20070626/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pinkandyellow.com/microsoft-expression/expression-web-what-a-bug-already-20070626/</link>
	<description>Tutorials and thoughts on Microsoft Expression, CSS and WordPress</description>
	<pubDate>Tue, 06 Jan 2009 06:29:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cheryl D Wise</title>
		<link>http://blog.pinkandyellow.com/microsoft-expression/expression-web-what-a-bug-already-20070626/comment-page-1/#comment-10</link>
		<dc:creator>Cheryl D Wise</dc:creator>
		<pubDate>Thu, 19 Jul 2007 15:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/microsoft-expression/expression-web-what-a-bug-already-20070626/#comment-10</guid>
		<description>What you are probably seeing or rather not seeing is probably the BOM or Byle Order Mark characters that notify the browser that the page uses UTF-8 encoding. Expression Web add it by default unless you have a meta element setting the characterset to something other than UTF-8 (which is the default for WordPress). Unfortuantely, there is no other way to turn off the BOM that is 100% sucessful. The product team is well aware of the BOM issue and the problems it causes in PHP. 

Simply uploading the file should not cause a BOM to appear but I am guessing you used Expression Web to edit your config.php file.  There are a few things you can do to make working wtih PHP files in the current version  some of which I have summarized at http://by-expression.com/tutorials/characterset/index.aspx</description>
		<content:encoded><![CDATA[<p>What you are probably seeing or rather not seeing is probably the BOM or Byle Order Mark characters that notify the browser that the page uses UTF-8 encoding. Expression Web add it by default unless you have a meta element setting the characterset to something other than UTF-8 (which is the default for WordPress). Unfortuantely, there is no other way to turn off the BOM that is 100% sucessful. The product team is well aware of the BOM issue and the problems it causes in PHP. </p>
<p>Simply uploading the file should not cause a BOM to appear but I am guessing you used Expression Web to edit your config.php file.  There are a few things you can do to make working wtih PHP files in the current version  some of which I have summarized at <a href="http://by-expression.com/tutorials/characterset/index.aspx" rel="nofollow">http://by-expression.com/tutorials/characterset/index.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Laberge</title>
		<link>http://blog.pinkandyellow.com/microsoft-expression/expression-web-what-a-bug-already-20070626/comment-page-1/#comment-2</link>
		<dc:creator>Paul Laberge</dc:creator>
		<pubDate>Wed, 27 Jun 2007 13:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pinkandyellow.com/microsoft-expression/expression-web-what-a-bug-already-20070626/#comment-2</guid>
		<description>Hi, Morten.

Thanks for trying out Expression Web!  Your assessment of Expression Web is very good - it's not a perfect product, but it's a good start.  While I haven't seen that behaviour before with PHP files, I will pass on your feedback to the Expression Web product team.

I know that there is an intent for full PHP support in the next major version of Expression Web, but that is a TBD right now.  It wouldn't surprise me if the support for PHP does in fact make it into v2.0, however, and I'm hoping that the product team has already caught this bug for the next release.  If they haven't, they will be notified of it by me.  :)

Thanks for coming to our event!  I'm glad it was useful and enjoyable for you!

Best regards,

Paul</description>
		<content:encoded><![CDATA[<p>Hi, Morten.</p>
<p>Thanks for trying out Expression Web!  Your assessment of Expression Web is very good - it&#8217;s not a perfect product, but it&#8217;s a good start.  While I haven&#8217;t seen that behaviour before with PHP files, I will pass on your feedback to the Expression Web product team.</p>
<p>I know that there is an intent for full PHP support in the next major version of Expression Web, but that is a TBD right now.  It wouldn&#8217;t surprise me if the support for PHP does in fact make it into v2.0, however, and I&#8217;m hoping that the product team has already caught this bug for the next release.  If they haven&#8217;t, they will be notified of it by me.  <img src='http://blog.pinkandyellow.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks for coming to our event!  I&#8217;m glad it was useful and enjoyable for you!</p>
<p>Best regards,</p>
<p>Paul</p>
]]></content:encoded>
	</item>
</channel>
</rss>
