<?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: Humane Text Formats</title>
	<atom:link href="http://bluebones.net/2005/02/humane-text-formats/feed/" rel="self" type="application/rss+xml" />
	<link>http://bluebones.net/2005/02/humane-text-formats/</link>
	<description>Adventures in Computer Programming</description>
	<pubDate>Wed, 20 Aug 2008 07:01:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Is HTML a Humane Markup Language? &#124; The CyberwBlog</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-22938</link>
		<dc:creator>Is HTML a Humane Markup Language? &#124; The CyberwBlog</dc:creator>
		<pubDate>Wed, 04 Jun 2008 19:29:01 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-22938</guid>
		<description>[...] Let&#8217;s consider a simpler example. What we&#8217;re looking for is some kind of middle ground, a humane text format. Let&#8217;s start with some basic HTML. [...]</description>
		<content:encoded><![CDATA[<p>[...] Let&#8217;s consider a simpler example. What we&#8217;re looking for is some kind of middle ground, a humane text format. Let&#8217;s start with some basic HTML. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is HTML a Humane Markup Language? - Programming</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-22909</link>
		<dc:creator>Is HTML a Humane Markup Language? - Programming</dc:creator>
		<pubDate>Wed, 04 Jun 2008 03:07:29 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-22909</guid>
		<description>[...] Let&#39;s consider a simpler example. What we&#39;re looking for is some kind of middle ground, a humane text format. Let&#39;s start with some basic HTML. [...]</description>
		<content:encoded><![CDATA[<p>[...] Let&#39;s consider a simpler example. What we&#39;re looking for is some kind of middle ground, a humane text format. Let&#39;s start with some basic HTML. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sweetraskels Blog&#187; Blog Archive &#187; Is HTML a Humane Markup Language?</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-22713</link>
		<dc:creator>Sweetraskels Blog&#187; Blog Archive &#187; Is HTML a Humane Markup Language?</dc:creator>
		<pubDate>Sat, 31 May 2008 09:33:51 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-22713</guid>
		<description>[...] Let&#8217;s consider a simpler example. What we&#8217;re looking for is some kind of middle ground, a humane text format. Let&#8217;s start with some basic HTML. [...]</description>
		<content:encoded><![CDATA[<p>[...] Let&#8217;s consider a simpler example. What we&#8217;re looking for is some kind of middle ground, a humane text format. Let&#8217;s start with some basic HTML. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-15410</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sat, 29 Dec 2007 04:44:23 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-15410</guid>
		<description>I went through a similar exercise, although I focused on Textile and Markdown because they are directly supported by Django which I use for web development. I am using Textile and it works well in general.

Markdown has an advantage that is specifically relevant to my application: if you want to allow other users to enter marked up text (e.g. article submissions) to your site, you want to be able to escape html so they can't do screwy things with your page layout. Textile uses quotes in URL syntax, which is one of the characters you need to escape to completely protect against embedded HTML errors. I believe that Markdown text can be completely escaped prior to processing into HTML, which effectively enforces Markdown-only markups.

For this reason I am considering changing from Textile to Markdown.

tim</description>
		<content:encoded><![CDATA[<p>I went through a similar exercise, although I focused on Textile and Markdown because they are directly supported by Django which I use for web development. I am using Textile and it works well in general.</p>
<p>Markdown has an advantage that is specifically relevant to my application: if you want to allow other users to enter marked up text (e.g. article submissions) to your site, you want to be able to escape html so they can&#8217;t do screwy things with your page layout. Textile uses quotes in URL syntax, which is one of the characters you need to escape to completely protect against embedded HTML errors. I believe that Markdown text can be completely escaped prior to processing into HTML, which effectively enforces Markdown-only markups.</p>
<p>For this reason I am considering changing from Textile to Markdown.</p>
<p>tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-2505</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Thu, 19 Oct 2006 20:34:24 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-2505</guid>
		<description>I think readability of code is an issue, and thats why any HTML helper tool won't be sufficient for a lot of us.
I get sick of everything being XML this and XML that, thankfully YAML/JSON seem to be getting used in some projects instead and hopefully the same goes for markup's like those mentioned here.

Embedded HTML was critical, which some text2html languages didn't have (but should have)
Personally, my use of tables leans me to Textile, but I will try Markdown and see how it goes also.

Great article!</description>
		<content:encoded><![CDATA[<p>I think readability of code is an issue, and thats why any HTML helper tool won&#8217;t be sufficient for a lot of us.<br />
I get sick of everything being XML this and XML that, thankfully YAML/JSON seem to be getting used in some projects instead and hopefully the same goes for markup&#8217;s like those mentioned here.</p>
<p>Embedded HTML was critical, which some text2html languages didn&#8217;t have (but should have)<br />
Personally, my use of tables leans me to Textile, but I will try Markdown and see how it goes also.</p>
<p>Great article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xah lee</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-2379</link>
		<dc:creator>xah lee</dc:creator>
		<pubDate>Mon, 09 Oct 2006 03:11:27 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-2379</guid>
		<description>Or, you could and probably should, use a HTML helping editor, such as Emacs. When such a editor is well done, it takes away the pain of writing the markup. It is, after all, the sole intended purpose of such editors.

I introduce: Emacs and HTML
http://xahlee.org/emacs/emacs_html.html

  Xah
  xah@xahlee.org
∑ http://xahlee.org/</description>
		<content:encoded><![CDATA[<p>Or, you could and probably should, use a HTML helping editor, such as Emacs. When such a editor is well done, it takes away the pain of writing the markup. It is, after all, the sole intended purpose of such editors.</p>
<p>I introduce: Emacs and HTML<br />
<a href="http://xahlee.org/emacs/emacs_html.html" rel="nofollow">http://xahlee.org/emacs/emacs_html.html</a></p>
<p>  Xah<br />
  <a href="mailto:xah@xahlee.org">xah@xahlee.org</a><br />
∑ <a href="http://xahlee.org/" rel="nofollow">http://xahlee.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Narebski</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-1153</link>
		<dc:creator>Jakub Narebski</dc:creator>
		<pubDate>Thu, 18 May 2006 13:09:20 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-1153</guid>
		<description>What about AsciiDoc (http://www.methods.co.nz/asciidoc/), how it compares to mentioned formats? I know it has output/conversion to PDF, XHTML, HTML Help, manpage or plain text.</description>
		<content:encoded><![CDATA[<p>What about AsciiDoc (http://www.methods.co.nz/asciidoc/), how it compares to mentioned formats? I know it has output/conversion to PDF, XHTML, HTML Help, manpage or plain text.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas David Baker</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-321</link>
		<dc:creator>Thomas David Baker</dc:creator>
		<pubDate>Wed, 03 Aug 2005 08:17:56 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-321</guid>
		<description>Thanks for letting me know.  I've corrected the table above.</description>
		<content:encoded><![CDATA[<p>Thanks for letting me know.  I&#8217;ve corrected the table above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcelo Huerta</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-320</link>
		<dc:creator>Marcelo Huerta</dc:creator>
		<pubDate>Wed, 03 Aug 2005 03:53:20 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-320</guid>
		<description>You are wrong on two counts about reStructuredText.

1. The class atribute is supported, with the class:: directive (for paragraphs) and the definition of roles (for spans).

2. There are 'id' definitions... but they are autogenerated.</description>
		<content:encoded><![CDATA[<p>You are wrong on two counts about reStructuredText.</p>
<p>1. The class atribute is supported, with the class:: directive (for paragraphs) and the definition of roles (for spans).</p>
<p>2. There are &#8216;id&#8217; definitions&#8230; but they are autogenerated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas David Baker</title>
		<link>http://bluebones.net/2005/02/humane-text-formats/#comment-248</link>
		<dc:creator>Thomas David Baker</dc:creator>
		<pubDate>Tue, 15 Mar 2005 17:20:29 +0000</pubDate>
		<guid isPermaLink="false">/?p=94#comment-248</guid>
		<description>Well, I've written a couple of posts here and a good few other text files recently and apart from underlying the section headings with equals and then dashes for the subsections my foray into humane text formats has left me in pretty much the same positionas I was before I started: plain text becomes pseudo XHTML at the first sign of a link and then at the end I go through and clean it all up to valid XHTML. So I seem to have followed your path too.</description>
		<content:encoded><![CDATA[<p>Well, I&#8217;ve written a couple of posts here and a good few other text files recently and apart from underlying the section headings with equals and then dashes for the subsections my foray into humane text formats has left me in pretty much the same positionas I was before I started: plain text becomes pseudo XHTML at the first sign of a link and then at the end I go through and clean it all up to valid XHTML. So I seem to have followed your path too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
