<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.6" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Notebook Markup: Headers and Whitespace</title>
	<link>http://www.foothills.wjduquette.com/blog/archives/1469</link>
	<description>A tiny principality in the Commonwealth of Letters</description>
	<pubDate>Fri, 05 Dec 2008 02:57:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.6</generator>

	<item>
		<title>by: Will Duquette</title>
		<link>http://www.foothills.wjduquette.com/blog/archives/1469#comment-113602</link>
		<pubDate>Wed, 28 Nov 2007 20:44:30 +0000</pubDate>
		<guid>http://www.foothills.wjduquette.com/blog/archives/1469#comment-113602</guid>
					<description>The text widget isn't an issue; nbm3 markup will always be rendered via conversion to HTML as displayed by Tkhtml3, and mediated by a special
CSS style sheet.  Thus, it's conceivable that the user could be allowed to specify additional CSS styles, overriding the defaults.

I'll think about this.</description>
		<content:encoded><![CDATA[<p>The text widget isn&#8217;t an issue; nbm3 markup will always be rendered via conversion to HTML as displayed by Tkhtml3, and mediated by a special<br />
CSS style sheet.  Thus, it&#8217;s conceivable that the user could be allowed to specify additional CSS styles, overriding the defaults.</p>
<p>I&#8217;ll think about this.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Andreas Kupries</title>
		<link>http://www.foothills.wjduquette.com/blog/archives/1469#comment-113555</link>
		<pubDate>Wed, 28 Nov 2007 18:33:40 +0000</pubDate>
		<guid>http://www.foothills.wjduquette.com/blog/archives/1469#comment-113555</guid>
					<description>I would go for the HTML behaviour, alwas whitespace before and after, amount possibly dependent on the level of the header (*). I think that this more in line with typographical conventions.


(*) Is that something which could be left to a CSS file ? (For HTML only, Text widget ... Tags can do that, right ? So the set of tag configuration woulds essentially be a style).</description>
		<content:encoded><![CDATA[<p>I would go for the HTML behaviour, alwas whitespace before and after, amount possibly dependent on the level of the header (*). I think that this more in line with typographical conventions.</p>
<p>(*) Is that something which could be left to a CSS file ? (For HTML only, Text widget &#8230; Tags can do that, right ? So the set of tag configuration woulds essentially be a style).
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
