<?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"
	>
<channel>
	<title>Comments on: Welcome to the new Opera Watch</title>
	<atom:link href="http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html/feed" rel="self" type="application/rss+xml" />
	<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html</link>
	<description>A blog covering the latest buzz on the Opera browser and its competition.</description>
	<pubDate>Tue, 06 Jan 2009 03:36:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Tzach</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3794</link>
		<dc:creator>Tzach</dc:creator>
		<pubDate>Wed, 03 May 2006 20:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3794</guid>
		<description>How come there are no IE explorer users commentators?!</description>
		<content:encoded><![CDATA[<p>How come there are no IE explorer users commentators?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mollusca</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3780</link>
		<dc:creator>mollusca</dc:creator>
		<pubDate>Wed, 03 May 2006 06:44:33 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3780</guid>
		<description>Awesome! How about more frequent posts ;)</description>
		<content:encoded><![CDATA[<p>Awesome! How about more frequent posts <img src='http://operawatch.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramunas</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3773</link>
		<dc:creator>Ramunas</dc:creator>
		<pubDate>Tue, 02 May 2006 13:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3773</guid>
		<description>Nice new look. Keep it up. :)</description>
		<content:encoded><![CDATA[<p>Nice new look. Keep it up. <img src='http://operawatch.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Goldman</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3772</link>
		<dc:creator>Daniel Goldman</dc:creator>
		<pubDate>Tue, 02 May 2006 12:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3772</guid>
		<description>Kelson, Thanks for looking into the problem. I'll take a look at the nbsp issue.

Also, I'm not sure it was an Opera problem. I think I also had it with IE.</description>
		<content:encoded><![CDATA[<p>Kelson, Thanks for looking into the problem. I&#8217;ll take a look at the nbsp issue.</p>
<p>Also, I&#8217;m not sure it was an Opera problem. I think I also had it with IE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jamie</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3770</link>
		<dc:creator>jamie</dc:creator>
		<pubDate>Tue, 02 May 2006 09:06:08 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3770</guid>
		<description>nice one, the new design looks great :)</description>
		<content:encoded><![CDATA[<p>nice one, the new design looks great <img src='http://operawatch.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Medina</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3769</link>
		<dc:creator>Medina</dc:creator>
		<pubDate>Tue, 02 May 2006 06:51:37 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3769</guid>
		<description>Am I late again?</description>
		<content:encoded><![CDATA[<p>Am I late again?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelson</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3768</link>
		<dc:creator>Kelson</dc:creator>
		<pubDate>Tue, 02 May 2006 05:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3768</guid>
		<description>Looks like it's a bug in either &lt;a href="http://tinymce.moxiecode.com/" rel="nofollow"&gt;TinyMCE&lt;/a&gt; (the editor that WordPress uses for WYSIWYG posting) or &lt;a href="http://nontroppo.org/wiki/TextAreaEditor" rel="nofollow"&gt;Opera 9's support for designMode&lt;/a&gt;.  I was able to reproduce the problem at TinyMCE's &lt;a href="http://tinymce.moxiecode.com/example_full.php?example=true" rel="nofollow"&gt;example page&lt;/a&gt;.  It looks like either TinyMCE or designMode is set so that if you type two spaces in a row, the second one is done as &lt;code&gt;&#38;nbsp;&lt;/code&gt; (a non-breaking space) instead of a plain space.  This would be so that you can do things like insert two spaces after a period and get the proper spacing.

As near as I can tell, what's happening is that the Opera/TinyMCE combination is instead using a &lt;code&gt;&#38;nbsp;&lt;/code&gt; any time there are two "spaces" in a row---and it's counting line breaks.  So if you start typing at the end of the text area, it's fine, but if you go back and start typing at the end of a line, all the spaces get inserted incorrectly.  There's only one flaw in this theory, and that's the fact that if I enable the WYSIWYG editor on my own site, the bug doesn't follow this pattern.

I know support for Opera in TinyMCE is new, since it relies on designMode, which is new in Opera 9.  So I don't know whether it's a flaw in Opera's implementation of designMode, or a flaw in the way TinyMCE interacts with Opera.

I did look at the JavaScript code for the version of TinyMCE that's included in WordPress, and I found what looks like a disabled workaround for a similar problem in Gecko on line 967 of /wp-includes/js/tinymce/tiny_mce.js -- but re-enabling it and setting it to check isOpera instead of isGecko didn't have any effect on the problem.

(Personally, I disabled the WYSIWYG editor shortly after upgrading to WordPress 2.0 because I didn't like the code it generated.  That, and I'm so used to HTML that typing the code was faster than trying to use the toolbar.)</description>
		<content:encoded><![CDATA[<p>Looks like it&#8217;s a bug in either <a href="http://tinymce.moxiecode.com/">TinyMCE</a> (the editor that WordPress uses for WYSIWYG posting) or <a href="http://nontroppo.org/wiki/TextAreaEditor">Opera 9&#8217;s support for designMode</a>.  I was able to reproduce the problem at TinyMCE&#8217;s <a href="http://tinymce.moxiecode.com/example_full.php?example=true">example page</a>.  It looks like either TinyMCE or designMode is set so that if you type two spaces in a row, the second one is done as <code>&amp;nbsp;</code> (a non-breaking space) instead of a plain space.  This would be so that you can do things like insert two spaces after a period and get the proper spacing.</p>
<p>As near as I can tell, what&#8217;s happening is that the Opera/TinyMCE combination is instead using a <code>&amp;nbsp;</code> any time there are two &#8220;spaces&#8221; in a row&#8212;and it&#8217;s counting line breaks.  So if you start typing at the end of the text area, it&#8217;s fine, but if you go back and start typing at the end of a line, all the spaces get inserted incorrectly.  There&#8217;s only one flaw in this theory, and that&#8217;s the fact that if I enable the WYSIWYG editor on my own site, the bug doesn&#8217;t follow this pattern.</p>
<p>I know support for Opera in TinyMCE is new, since it relies on designMode, which is new in Opera 9.  So I don&#8217;t know whether it&#8217;s a flaw in Opera&#8217;s implementation of designMode, or a flaw in the way TinyMCE interacts with Opera.</p>
<p>I did look at the JavaScript code for the version of TinyMCE that&#8217;s included in WordPress, and I found what looks like a disabled workaround for a similar problem in Gecko on line 967 of /wp-includes/js/tinymce/tiny_mce.js &#8212; but re-enabling it and setting it to check isOpera instead of isGecko didn&#8217;t have any effect on the problem.</p>
<p>(Personally, I disabled the WYSIWYG editor shortly after upgrading to WordPress 2.0 because I didn&#8217;t like the code it generated.  That, and I&#8217;m so used to HTML that typing the code was faster than trying to use the toolbar.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Goldman</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3766</link>
		<dc:creator>Daniel Goldman</dc:creator>
		<pubDate>Tue, 02 May 2006 00:49:59 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3766</guid>
		<description>Kelson, it happened with the WYSIWYG editor. The problem wasn't with long urls, it was just with plain words. Every so often, wordpress would recognize a bunch of words in a sentance as one word without any spaces.</description>
		<content:encoded><![CDATA[<p>Kelson, it happened with the WYSIWYG editor. The problem wasn&#8217;t with long urls, it was just with plain words. Every so often, wordpress would recognize a bunch of words in a sentance as one word without any spaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelson</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3765</link>
		<dc:creator>Kelson</dc:creator>
		<pubDate>Tue, 02 May 2006 00:44:48 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3765</guid>
		<description>Daniel: is that on the WYSIWYG editor, or the plain-text editor?  I know the plain-text editor has some problems, at least in Firefox, where the text area keeps snapping back to th left edge when I scroll it to view long URLs, but I've found the WYSYWIG editor annoying enough that I disabled it pretty quickly.

Or was it on the actual post/preview page?</description>
		<content:encoded><![CDATA[<p>Daniel: is that on the WYSIWYG editor, or the plain-text editor?  I know the plain-text editor has some problems, at least in Firefox, where the text area keeps snapping back to th left edge when I scroll it to view long URLs, but I&#8217;ve found the WYSYWIG editor annoying enough that I disabled it pretty quickly.</p>
<p>Or was it on the actual post/preview page?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamalesh</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3761</link>
		<dc:creator>Kamalesh</dc:creator>
		<pubDate>Mon, 01 May 2006 23:04:04 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3761</guid>
		<description>Great work, Daniel! Thanks for a great Opera blog to get the latest on a great browser and the team developing it...

(Nice layout/graphics by &lt;i&gt;EC&lt;/i&gt; and Dhalvat, as well.)

Wow, cool live comment preview and auto-gen browser/OS info, too...</description>
		<content:encoded><![CDATA[<p>Great work, Daniel! Thanks for a great Opera blog to get the latest on a great browser and the team developing it&#8230;</p>
<p>(Nice layout/graphics by <i>EC</i> and Dhalvat, as well.)</p>
<p>Wow, cool live comment preview and auto-gen browser/OS info, too&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan "d3bruts1d" McDaniel</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3760</link>
		<dc:creator>Bryan "d3bruts1d" McDaniel</dc:creator>
		<pubDate>Mon, 01 May 2006 22:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3760</guid>
		<description>Looks good Daniel!</description>
		<content:encoded><![CDATA[<p>Looks good Daniel!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3756</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Mon, 01 May 2006 21:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3756</guid>
		<description>Completely off-topic... I can't believe there are only four of us using Opera 8.54! I didn't think so many people would hop on to a beta!</description>
		<content:encoded><![CDATA[<p>Completely off-topic&#8230; I can&#8217;t believe there are only four of us using Opera 8.54! I didn&#8217;t think so many people would hop on to a beta!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Goldman</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3755</link>
		<dc:creator>Daniel Goldman</dc:creator>
		<pubDate>Mon, 01 May 2006 20:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3755</guid>
		<description>Kelson, the posts that are up now are all fine. However, during my tests, I have encountered this problem, where the line overflows and creates a long horizontal scrollbar.

It appears to me that wordpress thinks the whole line is one word, with no spaces. If I double click on a word in the editor, it's supposed to select only that word. However, if I click on a word in the long line, many words get selected.</description>
		<content:encoded><![CDATA[<p>Kelson, the posts that are up now are all fine. However, during my tests, I have encountered this problem, where the line overflows and creates a long horizontal scrollbar.</p>
<p>It appears to me that wordpress thinks the whole line is one word, with no spaces. If I double click on a word in the editor, it&#8217;s supposed to select only that word. However, if I click on a word in the long line, many words get selected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelson</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3754</link>
		<dc:creator>Kelson</dc:creator>
		<pubDate>Mon, 01 May 2006 20:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3754</guid>
		<description>Congrats on the site!

As for WordPress and word wrap... it looks OK, at least on this post.  what is it that you're having trouble with?  At least with the default setup, it will convert returns to line breaks, double-returns to paragraphs, and if you just type without hitting enter, it'll wrap it normally.  (Assuming you're using the plain posting interface, anyway.)

If you want to justify the text, that's done in the CSS file for the theme you're using.  Look for a &lt;code&gt;.post {...}&lt;/code&gt; section and add &lt;code&gt;text-align: justify;&lt;/code&gt; line between the curly braces.  You could do th same thing for comments by editing the &lt;code&gt;.comments {...}&lt;/code&gt; section.</description>
		<content:encoded><![CDATA[<p>Congrats on the site!</p>
<p>As for WordPress and word wrap&#8230; it looks OK, at least on this post.  what is it that you&#8217;re having trouble with?  At least with the default setup, it will convert returns to line breaks, double-returns to paragraphs, and if you just type without hitting enter, it&#8217;ll wrap it normally.  (Assuming you&#8217;re using the plain posting interface, anyway.)</p>
<p>If you want to justify the text, that&#8217;s done in the CSS file for the theme you&#8217;re using.  Look for a <code>.post {...}</code> section and add <code>text-align: justify;</code> line between the curly braces.  You could do th same thing for comments by editing the <code>.comments {...}</code> section.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://operawatch.com/news/2006/04/welcome-to-the-new-opera-watch.html#comment-3747</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Mon, 01 May 2006 13:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://alpha.opera-watch.com/news/2006/04/welcome-to-operawatchcom.html#comment-3747</guid>
		<description>Congrats! I like the new design!</description>
		<content:encoded><![CDATA[<p>Congrats! I like the new design!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
