<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for micycle</title>
	<atom:link href="http://micycle.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://micycle.wordpress.com</link>
	<description>themes will emerge over time</description>
	<lastBuildDate>Mon, 22 Dec 2008 09:29:23 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Newsmixer and Facebook Connect by Michael Kowalski</title>
		<link>http://micycle.wordpress.com/2008/12/21/newsmixer-and-facebook-connect/#comment-15</link>
		<dc:creator>Michael Kowalski</dc:creator>
		<pubDate>Mon, 22 Dec 2008 09:29:23 +0000</pubDate>
		<guid isPermaLink="false">http://micycle.wordpress.com/?p=149#comment-15</guid>
		<description>Update: this makes it look as if integrating Facebook Connect is pretty trivial:
http://nyquistrate.com/django/facebook-connect/</description>
		<content:encoded><![CDATA[<p>Update: this makes it look as if integrating Facebook Connect is pretty trivial:<br />
<a href="http://nyquistrate.com/django/facebook-connect/" rel="nofollow">http://nyquistrate.com/django/facebook-connect/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Ian Hickson is wrong about br and p tags by Michael Kowalski</title>
		<link>http://micycle.wordpress.com/2008/09/11/why-ian-hickson-is-wrong-about-br-and-p-tags/#comment-3</link>
		<dc:creator>Michael Kowalski</dc:creator>
		<pubDate>Fri, 12 Sep 2008 19:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://micycle.wordpress.com/?p=69#comment-3</guid>
		<description>In what way is a magic key combination acceptable? It has no visible affordance in the interface at all! Microsoft Word may indeed follow this practice, but I wonder how many Word users even know about it?

You might be correct about typography (for whatever that&#039;s worth, on the web; surely at least partly a matter of taste?), but you&#039;re missing my point, which is that we don&#039;t &lt;em&gt;know&lt;/em&gt; that they &lt;em&gt;are&lt;/em&gt; paragraphs! Inserting semantic markup tags does not mean your markup is semantically correct unless the markup actually reflects the author&#039;s intention.</description>
		<content:encoded><![CDATA[<p>In what way is a magic key combination acceptable? It has no visible affordance in the interface at all! Microsoft Word may indeed follow this practice, but I wonder how many Word users even know about it?</p>
<p>You might be correct about typography (for whatever that&#8217;s worth, on the web; surely at least partly a matter of taste?), but you&#8217;re missing my point, which is that we don&#8217;t <em>know</em> that they <em>are</em> paragraphs! Inserting semantic markup tags does not mean your markup is semantically correct unless the markup actually reflects the author&#8217;s intention.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Ian Hickson is wrong about br and p tags by lachlanhunt</title>
		<link>http://micycle.wordpress.com/2008/09/11/why-ian-hickson-is-wrong-about-br-and-p-tags/#comment-2</link>
		<dc:creator>lachlanhunt</dc:creator>
		<pubDate>Fri, 12 Sep 2008 10:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://micycle.wordpress.com/?p=69#comment-2</guid>
		<description>Typing Enter for a paragraph and Shift+Enter for a line break is acceptable UI.  (That is, in fact, how Microsoft Word behaves by default, although they set the default paragraph margins to 0, which makes it less noticable).  Alternatively, converting 2 sequential line breaks into a paragraph is another possibility, and is generally what is done when converting plain text inputs into HTML.

But using two br elements for a paragraph break is wrong, both semantically and typographically.  For readability, the spacing between 2 paragraphs should be less than the line-height.</description>
		<content:encoded><![CDATA[<p>Typing Enter for a paragraph and Shift+Enter for a line break is acceptable UI.  (That is, in fact, how Microsoft Word behaves by default, although they set the default paragraph margins to 0, which makes it less noticable).  Alternatively, converting 2 sequential line breaks into a paragraph is another possibility, and is generally what is done when converting plain text inputs into HTML.</p>
<p>But using two br elements for a paragraph break is wrong, both semantically and typographically.  For readability, the spacing between 2 paragraphs should be less than the line-height.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
