<?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: reStructuredText for blog post formatting</title>
	<atom:link href="http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/feed/" rel="self" type="application/rss+xml" />
	<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/</link>
	<description>Eli Bendersky's personal website</description>
	<lastBuildDate>Wed, 10 Mar 2010 17:32:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: eliben</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-155116</link>
		<dc:creator>eliben</dc:creator>
		<pubDate>Sun, 08 Feb 2009 18:15:46 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-155116</guid>
		<description>Hi Jason, thanks for commenting!

I&#039;m glad to hear that Textile has moved forward - it&#039;s a real shame it was neglected for so long.

Personally, I&#039;m very happy with reST now, and am using it for all my formatting needs.</description>
		<content:encoded><![CDATA[<p>Hi Jason, thanks for commenting!</p>
<p>I&#8217;m glad to hear that Textile has moved forward &#8211; it&#8217;s a real shame it was neglected for so long.</p>
<p>Personally, I&#8217;m very happy with reST now, and am using it for all my formatting needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Samsa</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-154980</link>
		<dc:creator>Jason Samsa</dc:creator>
		<pubDate>Sun, 08 Feb 2009 01:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-154980</guid>
		<description>Around the time of this post I took over the pytextile project.  Since taking it over, I&#039;ve completely rewritten  a port of Textile 2.0 to Python and have built a lot of tests around the code.  Some issues still exist but I think the current implementation (2.1.3) is much improved over past versions.  It doesn&#039;t have some of the non-textile features that existed in previous versions, but it does core textile much better.

It would be nice to allow pluggable extensions so that advanced users can customize pytextile easily.  Perhaps that will be a feature I build this year.</description>
		<content:encoded><![CDATA[<p>Around the time of this post I took over the pytextile project.  Since taking it over, I&#8217;ve completely rewritten  a port of Textile 2.0 to Python and have built a lot of tests around the code.  Some issues still exist but I think the current implementation (2.1.3) is much improved over past versions.  It doesn&#8217;t have some of the non-textile features that existed in previous versions, but it does core textile much better.</p>
<p>It would be nice to allow pluggable extensions so that advanced users can customize pytextile easily.  Perhaps that will be a feature I build this year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vasudev Ram</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-128532</link>
		<dc:creator>Vasudev Ram</dc:creator>
		<pubDate>Mon, 01 Sep 2008 00:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-128532</guid>
		<description>Thanks, Eli. Did a quick check - looks fine now.
Will let you know if any other issues are found.

- Vasudev</description>
		<content:encoded><![CDATA[<p>Thanks, Eli. Did a quick check &#8211; looks fine now.<br />
Will let you know if any other issues are found.</p>
<p>- Vasudev</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eliben</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-127940</link>
		<dc:creator>eliben</dc:creator>
		<pubDate>Tue, 26 Aug 2008 15:13:17 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-127940</guid>
		<description>Vasudev: yes, this is a limitation of those HTML text boxes, and I don&#039;t know if I can do much about it. You can always copy-paste the whole code and view it comfortably in an outside editor if the scrolling becomes a real problem.

&lt;strong&gt;Update&lt;/strong&gt;: I think I&#039;ve managed to limit the height of the &#039;pre&#039; boxes (using the max-height CSS property). I hope it works out nicely now.</description>
		<content:encoded><![CDATA[<p>Vasudev: yes, this is a limitation of those HTML text boxes, and I don&#8217;t know if I can do much about it. You can always copy-paste the whole code and view it comfortably in an outside editor if the scrolling becomes a real problem.</p>
<p><strong>Update</strong>: I think I&#8217;ve managed to limit the height of the &#8216;pre&#8217; boxes (using the max-height CSS property). I hope it works out nicely now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vasudev Ram</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-127904</link>
		<dc:creator>Vasudev Ram</dc:creator>
		<pubDate>Tue, 26 Aug 2008 10:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-127904</guid>
		<description>Checked again after getting a message from Eli - there is a scroll bar at the bottom of the box, but missed seeing it, either due to a hurry or because it isn&#039;t visible when you&#039;re viewing the top or middle of the code (since the box is tall).</description>
		<content:encoded><![CDATA[<p>Checked again after getting a message from Eli &#8211; there is a scroll bar at the bottom of the box, but missed seeing it, either due to a hurry or because it isn&#8217;t visible when you&#8217;re viewing the top or middle of the code (since the box is tall).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vasudev Ram</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-127892</link>
		<dc:creator>Vasudev Ram</dc:creator>
		<pubDate>Tue, 26 Aug 2008 09:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-127892</guid>
		<description>Interesting post, Eli.

Coincidentally, I had been thinking about the same issue - generating content for blog posts from some form of structured text such as Textile or Markdown - just a little while before I read this post. Though I knew about reST (reStructuredText), for some reason I hadn&#039;t remembered that option - so its good that I read your post ...

With my PC config, I see an issue with the output you got - i.e. this current post:

The code shown is truncated on the right side. I tried resizing the text (using Firefox) with Ctrl-plus and Ctrl-minus, to different sizes, but the problem stays.

The text (English) content of the post shows fine, though.

- Vasudev</description>
		<content:encoded><![CDATA[<p>Interesting post, Eli.</p>
<p>Coincidentally, I had been thinking about the same issue &#8211; generating content for blog posts from some form of structured text such as Textile or Markdown &#8211; just a little while before I read this post. Though I knew about reST (reStructuredText), for some reason I hadn&#8217;t remembered that option &#8211; so its good that I read your post &#8230;</p>
<p>With my PC config, I see an issue with the output you got &#8211; i.e. this current post:</p>
<p>The code shown is truncated on the right side. I tried resizing the text (using Firefox) with Ctrl-plus and Ctrl-minus, to different sizes, but the problem stays.</p>
<p>The text (English) content of the post shows fine, though.</p>
<p>- Vasudev</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eliben</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-127838</link>
		<dc:creator>eliben</dc:creator>
		<pubDate>Mon, 25 Aug 2008 17:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-127838</guid>
		<description>John: Indeed, it seems that publishing only the body fragment without the programmatic interface is impossible. 

I don&#039;t have PyPi experience, but from what I&#039;ve seen the author of reST is very responsive, and you should definitely tell him the idea you have. He&#039;ll probably add it as a command line option to the published script.

Valentin: I don&#039;t like WYSIWYGs :-) They&#039;re all good and nice while they serve your need. But once there&#039;s something you can&#039;t do with them, that&#039;s it, you&#039;re done. For example, I found no normal way to conveniently post source code and footnotes with Wordpress&#039;s WYSIWYG.</description>
		<content:encoded><![CDATA[<p>John: Indeed, it seems that publishing only the body fragment without the programmatic interface is impossible. </p>
<p>I don&#8217;t have PyPi experience, but from what I&#8217;ve seen the author of reST is very responsive, and you should definitely tell him the idea you have. He&#8217;ll probably add it as a command line option to the published script.</p>
<p>Valentin: I don&#8217;t like WYSIWYGs <img src='http://eli.thegreenplace.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  They&#8217;re all good and nice while they serve your need. But once there&#8217;s something you can&#8217;t do with them, that&#8217;s it, you&#8217;re done. For example, I found no normal way to conveniently post source code and footnotes with Wordpress&#8217;s WYSIWYG.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valentin Jacquemin</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-127811</link>
		<dc:creator>Valentin Jacquemin</dc:creator>
		<pubDate>Mon, 25 Aug 2008 12:04:19 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-127811</guid>
		<description>Hello Eli,
I was just wondering... Why do you get tired by writing your posts in HTML since Wordpress has a great wysiwyg?</description>
		<content:encoded><![CDATA[<p>Hello Eli,<br />
I was just wondering&#8230; Why do you get tired by writing your posts in HTML since Wordpress has a great wysiwyg?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-127550</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 24 Aug 2008 20:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-127550</guid>
		<description>Edit: Sorry, don&#039;t want to sound harsh or rude, I just don&#039;t like to see a good markup format not be widely-used because people can&#039;t easily use it.

Edit #2: Also, it looks like the Cheeseshop is now instead called the &quot;python package index&quot;, or just &quot;package index&quot; for short.</description>
		<content:encoded><![CDATA[<p>Edit: Sorry, don&#8217;t want to sound harsh or rude, I just don&#8217;t like to see a good markup format not be widely-used because people can&#8217;t easily use it.</p>
<p>Edit #2: Also, it looks like the Cheeseshop is now instead called the &#8220;python package index&#8221;, or just &#8220;package index&#8221; for short.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/comment-page-1/#comment-127545</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 24 Aug 2008 20:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://eli.thegreenplace.net/2008/08/24/restructuredtext-for-blog-post-formatting/#comment-127545</guid>
		<description>I like reST, and I think -- formatting-wise -- it&#039;s a good alternative to Markdown. The reason reST is not more widely-used is because there&#039;s no easy way for non-technical users to just have a script that turns a reST-formatted document into an html fragment.

Markdown has this. It&#039;s just the Markdown.pl script from daringfireball. You download it and run it. Pass it a filename and out of stdout comes plain html (but no html or head tags, nor CSS -- just an html fragment).

Someone needs to write and distribute (via the Cheeseshop, please) a simple rst2htmlfrag.py script that does what Markdown.pl does (but for reST).

Incidentally, no, I have no idea why the bundled rst2html.py tool does not feature an &quot;--html-fragment-only&quot; option. (Or, if it has such an option, I&#039;m not seeing it in the online help.)

And, please, don&#039;t tell me it&#039;s trivial to write such a script. I realize it&#039;s trivial for someone who knows a little bit of python and who&#039;s willing to dig around the docutils docs. Maybe it&#039;s so darn trivial that no one thinks they need to do it and so very few users consider using reST when comparing it to Markdown, Textile, asciidoc, etc.

Eli, maybe this would be a good exercise for you if you&#039;ve never packaged and uploaded to the cheeseshop.</description>
		<content:encoded><![CDATA[<p>I like reST, and I think &#8212; formatting-wise &#8212; it&#8217;s a good alternative to Markdown. The reason reST is not more widely-used is because there&#8217;s no easy way for non-technical users to just have a script that turns a reST-formatted document into an html fragment.</p>
<p>Markdown has this. It&#8217;s just the Markdown.pl script from daringfireball. You download it and run it. Pass it a filename and out of stdout comes plain html (but no html or head tags, nor CSS &#8212; just an html fragment).</p>
<p>Someone needs to write and distribute (via the Cheeseshop, please) a simple rst2htmlfrag.py script that does what Markdown.pl does (but for reST).</p>
<p>Incidentally, no, I have no idea why the bundled rst2html.py tool does not feature an &#8220;&#8211;html-fragment-only&#8221; option. (Or, if it has such an option, I&#8217;m not seeing it in the online help.)</p>
<p>And, please, don&#8217;t tell me it&#8217;s trivial to write such a script. I realize it&#8217;s trivial for someone who knows a little bit of python and who&#8217;s willing to dig around the docutils docs. Maybe it&#8217;s so darn trivial that no one thinks they need to do it and so very few users consider using reST when comparing it to Markdown, Textile, asciidoc, etc.</p>
<p>Eli, maybe this would be a good exercise for you if you&#8217;ve never packaged and uploaded to the cheeseshop.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
