<?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: How BibDesk generates Apple Help and a web manual</title>
	<atom:link href="http://michael-mccracken.net/2010/02/how-bibdesk-generates-apple-help-and-a-web-manual/feed/" rel="self" type="application/rss+xml" />
	<link>http://michael-mccracken.net/2010/02/how-bibdesk-generates-apple-help-and-a-web-manual/</link>
	<description>This is a weblog</description>
	<lastBuildDate>Mon, 06 Feb 2012 22:21:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Kevin Grant</title>
		<link>http://michael-mccracken.net/2010/02/how-bibdesk-generates-apple-help-and-a-web-manual/comment-page-1/#comment-1039</link>
		<dc:creator>Kevin Grant</dc:creator>
		<pubDate>Mon, 22 Feb 2010 01:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://michael-mccracken.net/?p=264#comment-1039</guid>
		<description>&lt;p&gt;I had a similar problem in my project (also creating Apple Help pages), although I was mostly just looking for something that was more compact to maintain than HTML.&lt;/p&gt;

&lt;p&gt;I found Textile:
http://en.wikipedia.org/wiki/Textile_(markup_language)&lt;/p&gt;

&lt;p&gt;Specifically, the pytextile tool:
http://code.google.com/p/pytextile/&lt;/p&gt;

&lt;p&gt;Like in your case, I still felt that I needed a processing script and build step to make the most complete web pages.&lt;/p&gt;

&lt;p&gt;But in terms of input, the Textile format is pretty trivial; the most common page elements are reduced to one or two prefix characters most of the time, e.g. a list bullet is a &quot;*&quot;, a heading might be &quot;h1.&quot;.  And raw HTML can be directly embedded for corner cases.&lt;/p&gt;

&lt;p&gt;The other neat thing about the language is that it interprets intent pretty well, e.g. if you were to type &quot;2 x 3&quot;, it would assume that the &quot;x&quot; should become the Unicode multiplication sign in the HTML output; similarly, it handles curly quotes and other conversions implicitly from a raw ASCII line.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I had a similar problem in my project (also creating Apple Help pages), although I was mostly just looking for something that was more compact to maintain than HTML.</p>

<p>I found Textile:
<a href="http://en.wikipedia.org/wiki/Textile_(markup_language)" rel="nofollow">http://en.wikipedia.org/wiki/Textile_(markup_language)</a></p>

<p>Specifically, the pytextile tool:
<a href="http://code.google.com/p/pytextile/" rel="nofollow">http://code.google.com/p/pytextile/</a></p>

<p>Like in your case, I still felt that I needed a processing script and build step to make the most complete web pages.</p>

<p>But in terms of input, the Textile format is pretty trivial; the most common page elements are reduced to one or two prefix characters most of the time, e.g. a list bullet is a &#8220;*&#8221;, a heading might be &#8220;h1.&#8221;.  And raw HTML can be directly embedded for corner cases.</p>

<p>The other neat thing about the language is that it interprets intent pretty well, e.g. if you were to type &#8220;2 x 3&#8243;, it would assume that the &#8220;x&#8221; should become the Unicode multiplication sign in the HTML output; similarly, it handles curly quotes and other conversions implicitly from a raw ASCII line.</p>]]></content:encoded>
	</item>
</channel>
</rss>

