<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Markdown Community Group</title>
	<atom:link href="http://www.w3.org/community/markdown/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.w3.org/community/markdown</link>
	<description></description>
	<lastBuildDate>Mon, 26 Nov 2012 15:32:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>The group is now up and running</title>
		<link>http://www.w3.org/community/markdown/2012/11/21/the-group-is-now-up-and-running/</link>
		<comments>http://www.w3.org/community/markdown/2012/11/21/the-group-is-now-up-and-running/#comments</comments>
		<pubDate>Wed, 21 Nov 2012 12:38:06 +0000</pubDate>
		<dc:creator>Dave Pawson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/markdown/?p=41</guid>
		<description><![CDATA[As of 19 November the group is working towards a W3C Note. For conversations, see the mailing list. For longer term information, see the wiki pages. DaveP]]></description>
			<content:encoded><![CDATA[<p>As of 19 November the group is working towards a W3C Note.<br />
For conversations, see the mailing list. For longer term information, see the wiki pages.</p>
<p>DaveP</p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/markdown/2012/11/21/the-group-is-now-up-and-running/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A chrome issue</title>
		<link>http://www.w3.org/community/markdown/2012/10/26/a-chrome-issue/</link>
		<comments>http://www.w3.org/community/markdown/2012/10/26/a-chrome-issue/#comments</comments>
		<pubDate>Fri, 26 Oct 2012 18:08:54 +0000</pubDate>
		<dc:creator>Dave Pawson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/markdown/?p=33</guid>
		<description><![CDATA[Talking to Ian at W3C it seems that Google Chrome and IE9 have issues when editing Community pages. On Chrome I overcame this by allowing Chrome to load the page by selecting the small &#8216;shield&#8217; shape at the right hand &#8230; <a href="http://www.w3.org/community/markdown/2012/10/26/a-chrome-issue/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Talking to Ian at W3C it seems that Google Chrome and IE9 have issues when editing Community pages. On Chrome I overcame this by allowing Chrome to load the page by selecting the small &#8216;shield&#8217; shape at the right hand end of the address bar. This allows the group member to edit the text of pages.<br />
 It is currently being investigated by W3c</p>
<p>Nov 21 2012. This has now been resolved. DaveP</p>
<p>HTH</p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/markdown/2012/10/26/a-chrome-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Group formed for Markdown</title>
		<link>http://www.w3.org/community/markdown/2012/10/26/group-formed-for-markdown/</link>
		<comments>http://www.w3.org/community/markdown/2012/10/26/group-formed-for-markdown/#comments</comments>
		<pubDate>Fri, 26 Oct 2012 17:28:20 +0000</pubDate>
		<dc:creator>Dave Pawson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.w3.org/community/markdown/?p=21</guid>
		<description><![CDATA[Based on http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html a post by Jeff Atwood, where he introduces his ideas for standardizing Markdown for the future. Quote I don&#8217;t want to extend Markdown by adding tons of crazy new functionality, or radically change the way it currently &#8230; <a href="http://www.w3.org/community/markdown/2012/10/26/group-formed-for-markdown/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Based on<br />
http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html a<br />
post by Jeff Atwood, where he introduces his ideas for standardizing<br />
Markdown for the future. </p>
<p>Quote I don&#8217;t want to extend Markdown by adding tons of crazy new<br />
functionality, or radically change the way it currently works, or<br />
anything like that. I&#8217;d be opposed to such changes. I just want to<br />
solidify and standardize the simple, useful version of Markdown that<br />
is working so well for everyone right now. I want there to be an<br />
unambiguous, basic standard that everyone using Markdown can expect to<br />
work in the same way across all web sites in the world when they begin<br />
typing.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.w3.org/community/markdown/2012/10/26/group-formed-for-markdown/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
